1482 results found

1. In all SDKs for node and web implement industry best practice error reporting and error codes

   I have been working on multiple projects that use Firebase, I use the Firebase JS SDK and the Firebase Admin SDK. And I am always pulling my hair out with the error reporting and the ability to handle in the SDKs returned errors. This is especially annoying when using TypeScript.

   There is also no master list of all error codes that an SDK can produce. That means I can get random error that I have to back trace to then add handling for it. Also I have to infer types all the time instead of using instanceof to check if it is an SDK error and get TS support.

   1. Please document all the error codes that each SDK could produce.

   2. Add a page to the documentation site about Error handling in the SDK (helps to explain how it works in this SDK if not very obvious)

   3. Please add a proper typescript Error object to the SDK. This would be a class that extends Error object and for the code property has all the possible codes it can produce. By doing this, the developers will be required to add to the list of error codes that the SDK has on the error if they add a new code when then trigger the error handling code. This means that users as they upgrade get more options in the SDK that they can use to see the new error types that have occurred.

   4. Contribution policy on the GitHub library that describes the error handling approach that has been placed and the expectations that are required for future code inclusion. This stops this from going backwards.

   99/100 I want the error code only and adding either or both would save 100s of hours of hair pulling (I don't want to look like Frank van Puffelen to soon).

   I acknowledge that this has been partially done, but an overhaul that finishes it would be much appreciated.

   I have been working on multiple projects that use Firebase, I use the Firebase JS SDK and the Firebase Admin SDK. And I am always pulling my hair out with the error reporting and the ability to handle in the SDKs returned errors. This is especially annoying when using TypeScript.

   There is also no master list of all error codes that an SDK can produce. That means I can get random error that I have to back trace to then add handling for it. Also I have to infer types all the time instead of using instanceof to check if… more

   2 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  SDKs  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

2. acquires the domain iDXcopilot.com before another platform does so.

   Dear Google Developers Team,

   I wanted to take a moment to acknowledge the incredible work you've done on Project IDX. Your dedication to innovation and excellence is truly impressive.

   I also wanted to bring to your attention the availability of the domain name (iDXcopilot.com) I strongly believe that acquiring this domain would be a valuable asset for your project. It's a perfect match for your brand and would provide a clear and concise way for users to access your platform.

   I urge you to expedite the process of purchasing this domain before someone else does. Owning IDXcopilot.com would:

   • Enhance brand recognition and credibility
   • Provide a centralized hub for users to access your platform
   • Prevent potential competitors from utilizing a similar domain
   • Give you control over the online presence of your project

   Please consider acquiring the domain to further strengthen our community and enhance your project's success.

   Dear Google Developers Team,

   I wanted to take a moment to acknowledge the incredible work you've done on Project IDX. Your dedication to innovation and excellence is truly impressive.

   I also wanted to bring to your attention the availability of the domain name (iDXcopilot.com) I strongly believe that acquiring this domain would be a valuable asset for your project. It's a perfect match for your brand and would provide a clear and concise way for users to access your platform.

   I urge you to expedite the process of purchasing this domain before someone else does. Owning IDXcopilot.com would:

   • Enhance brand… more
   4 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   1 comment  ·  Firebase Studio  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

3. structure and organization of Firestore collections: documentation

   Normally documentation about collections is done in a 3rd party tool like notion, jira, google docs (or notepad for the brave ones).

   After a while this easily becomes inconsistent due to ongoing changes throughout the project development. The same way as we document code directly in the code file, it'd be great to document collections directly in the firestore console.

   For this, something simple like a text input would suffice (ideally with some minimal markdown, but not mandatory). If developers need to add more detailed info or explanations (and make use of charts, designs, videos, whatever) they could simply add a link and direct to their favourite documentation tool.

   This documentation would be useful to add information about
   - collection structure
   - document versioning (very important in NO-SQL when changes in structure happen between app versions)
   - triggers and updates with cloud functions (eg first document is written, then triggers a cloud function that does X, and document gets updated with information Y

   Normally documentation about collections is done in a 3rd party tool like notion, jira, google docs (or notepad for the brave ones).

   After a while this easily becomes inconsistent due to ongoing changes throughout the project development. The same way as we document code directly in the code file, it'd be great to document collections directly in the firestore console.

   For this, something simple like a text input would suffice (ideally with some minimal markdown, but not mandatory). If developers need to add more detailed info or explanations (and make use of charts, designs, videos, whatever) they could simply add… more

   1 vote

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Firestore  ·  Edit…  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

4. Add a Preview environment for App Hosting deployments.

   As a developer, I want to be able to deploy my Next.js web app hosted using App Hosting to a Preview "channel", similar to firebase hosting:channel:deploy in hosting.
   Thanks.

   26 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   3 comments  ·  App Hosting  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

5. Data connect support for Postgres instances outside Google Cloud

   It would be nice if we can set our custom Postgres instance connection string so that we can use postgres instances outside the Google Cloud infrastructure.

   7 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Data Connect  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

6. Workspace Appearance

   You know that many developers use VS Code and as a software student, I was using it before I met Project IDX. One of my habits is that after logging in to the workspace, I would like to have options such as terminal, help, execute code directly at the top, not with 3 lines, and it would be nice to log in by connecting directly to github in the settings section.

   1 vote

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Firebase Studio  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

7. Support Angular Internationalization

   At this point the build fails because of the error:

   Output directory is not of expected structure

   4 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  App Hosting  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

8. Firebase CLI (Python version) should provide debugging information

   Add better debugging information into Firebase CLI (Python) version. The CLI frequently throws the following error but does not provide any further information, even in debug mode.

   Failed to call quitquitquit. This often means the server failed to start request to http://127.0.0.1:8081/__/quitquitquit failed, reason: connect ECONNREFUSED 127.0.0.1:8081 {"message":"request to http://127.0.0.1:8081/__/quitquitquit failed, reason: connect ECONNREFUSED 127.0.0.1:8081","type":"system","errno":"ECONNREFUSED","code":"ECONNREFUSED"}

   or

   Error: User code failed to load. Cannot determine backend specification

   Details of the error can however be found in the GCP Console and Cloud Build. The same error messages should appear in the CLI as the Console is not a scalable way to maintain/deploy to production.

   Add better debugging information into Firebase CLI (Python) version. The CLI frequently throws the following error but does not provide any further information, even in debug mode.

   Failed to call quitquitquit. This often means the server failed to start request to http://127.0.0.1:8081/__/quitquitquit failed, reason: connect ECONNREFUSED 127.0.0.1:8081 {"message":"request to http://127.0.0.1:8081/__/quitquitquit failed, reason: connect ECONNREFUSED 127.0.0.1:8081","type":"system","errno":"ECONNREFUSED","code":"ECONNREFUSED"}

   or

   Error: User code failed to load. Cannot determine backend specification

   Details of the error can however be found in the GCP Console and Cloud Build. The same error messages should appear in the CLI as the Console is not a scalable way to maintain/deploy… more

   1 vote

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Firebase CLI  ·  Edit…  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

9. Django support for firebase app hosting

   Django is a very popular framework. It is likely the easiest one to get up and running with, also allowing reusing the code much better than other solutions. No need to say how big Python is and Django (and even Flask) will only become bigger and bigger. Firebase app hosting must support Django. Not tomorrow, now!

   2 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  App Hosting  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

10. [Email Verification] Need to have a param to set expiration time

    As of now, there is no way we can set a custom expiration time for the Email Signin with link authentication. Our use case is that we generate this link through admin sdk and then mail the users (as an invite).

    Hence, it becomes really important for us to have a custom expiration time.

    1 vote

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Authentication  ·  Edit…  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

11. remove recaptcha firebase phone auth flutter

    remove recaptcha firebase phone auth flutter

    1 vote

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    1 comment  ·  Authentication  ·  Edit…  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

12. Convenient File Manager in Mobile

    The interface should be more practical to see on mobile.

    I propose that at least, taking into account the limitations of cell phones at the

    3 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    1 comment  ·  Firebase Studio  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

13. Public IDX Template Submission

    Public IDX Template Submission

    Summary:

    Introduce a feature to allow the public to submit open-source contributions to the IDX platform through a simple and streamlined process using a GitHub link. This feature aims to encourage community contributions and enhance the platform's template repository.

    Details:

    1. Feature Name: Public IDX Template Submission

    2. Description:

       • Create a public interface where users can submit new templates to the IDX platform.
       • Allow users to submit their templates by providing a GitHub repository link.
       • Submitted templates should be reviewed and, if approved, added to the IDX platform’s template view.

    3. Goals:

       • Encourage community engagement and contributions.
       • Expand the variety and number of templates available on the IDX platform.
       • Simplify the process for submitting and reviewing new templates.

    4. Key Components:

       • Submission Form: A web form where users can enter their GitHub repository link and additional details about their template.
       • Review Workflow: A process for reviewing submitted templates to ensure quality and compatibility with the IDX platform.
       • Template Integration: Mechanism to integrate approved templates into the IDX template repository and make them available to users.

    5. User Flow:

       • User visits the Public IDX Template Submission page.
       • User fills out a form with the GitHub link to their template repository and other required information (e.g., template description, author details).
       • Submission is reviewed by the IDX team.
       • Approved templates are added to the template view and made publicly available.

    6. Technical Requirements:

       • Form Validation: Ensure the GitHub link and other inputs are valid.
       • Repository Access: Ability to clone and test the GitHub repository to verify the template.
       • Automated Tests: Run automated tests on submitted templates to ensure they meet quality standards.
       • Approval System: An interface for the IDX team to review and approve/reject submissions.
       • Notification System: Notify users about the status of their submission (e.g., received, approved, rejected).

    7. Mockup:

    Public IDX Template Submission Page:
    ```

    ---

    | Public IDX Template Submission |

    ---

    | Submit your open-source template to the IDX |
    | platform. Provide the GitHub link to your |
    | repository and fill out the required details.|

    ---

    | Form: |
    | [GitHub Repository Link] ___________________ |
    | [Template Description] ___________________ |
    | [Author Name] ___________________ |
    | [Submit Button] |

    ---

    
    8. **Potential Challenges**:
       - Ensuring the quality and security of submitted templates.
       - Managing the review process efficiently as submission volume increases.
    
    #### Additional Information:
    
    - **Link to GitHub Repository**: Users should submit the repository link in the following format: `https://github.com/user/repository`
    - **Submission Guidelines**: Provide clear guidelines on what makes a good template and the criteria for approval.
    - **Community Engagement**: Consider creating a forum or discussion board for users to discuss and share ideas about templates.
    

    Public IDX Template Submission

    Summary:

    Introduce a feature to allow the public to submit open-source contributions to the IDX platform through a simple and streamlined process using a GitHub link. This feature aims to encourage community contributions and enhance the platform's template repository.

    Details:

    1. Feature Name: Public IDX Template Submission

    2. Description:

       • Create a public interface where users can submit new templates to the IDX platform.
       • Allow users to submit their templates by providing a GitHub repository link.
       • Submitted templates should be reviewed and, if approved, added to the IDX platform’s template view.

    3. Goals:

       • Encourage community engagement and… more
    3 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Firebase Studio  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

14. How to access Android emulator?

    Hi,

    Currently, there is no way to access the Android emulator in IDX. I tried using the shortcut CTRL+SHIFT+P, but there is still no option to view the Android emulator preview.

    Not only the Android emulator preview, but I am also unable to access the Web preview. When clicking on 'Show Web preview', I get this error message: "Command 'Project IDX: Show Web Preview' resulted in an error: command 'monospace.showWebPreview' not found."

    Please help.

    1 vote

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Firebase Studio  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

15. Serverpod

    Certainly! Below is a template you can use to request adding Serverpod to the Google Cloud Index (IDX) platform. Customize it with specific details or additional information as needed:

    ---

    Subject: Request to Add Serverpod to Google Cloud Index (IDX) Platform

    I am writing to request the addition of Serverpod to the Google Cloud Index (IDX) platform. Serverpod is a robust backend framework designed specifically for Dart, leveraging the power of Flutter for its user interface. Given its features and compatibility with modern development practices, I believe it would be a valuable addition to the Google Cloud ecosystem.

    Key Features of Serverpod:

    1. Dart-Based Framework: Serverpod is built using Dart, providing seamless integration with Flutter for creating high-performance, scalable applications.
    2. PostgreSQL Database: It uses PostgreSQL as its primary database, ensuring reliable and efficient data management.
    3. Docker Support: Serverpod can be easily containerized using Docker, facilitating consistent development, testing, and deployment processes.
    4. Cloud Deployment: It supports deployment on various cloud platforms, including AWS and Google Cloud, enabling flexible and scalable infrastructure management.

    Benefits of Adding Serverpod to Google Cloud IDX:

    • Enhanced Developer Experience: Dart and Flutter developers will have a complete, integrated solution for building both frontend and backend components within the Google Cloud environment.
    • Scalability and Flexibility: Serverpod's compatibility with Docker and PostgreSQL ensures that applications can scale efficiently and leverage the full potential of cloud-native services.
    • Comprehensive Cloud Integration: By supporting Serverpod, Google Cloud can attract more developers who are looking for a unified development stack that leverages Google’s robust cloud infrastructure.

    I am confident that adding Serverpod to the Google Cloud IDX platform will significantly benefit the developer community and further enhance the capabilities of Google Cloud services.

    Thank you for considering my request. I am looking forward to seeing Serverpod as part of the Google Cloud IDX platform. Please let me know if you need any additional information or have any questions.

    Certainly! Below is a template you can use to request adding Serverpod to the Google Cloud Index (IDX) platform. Customize it with specific details or additional information as needed:

    ---

    Subject: Request to Add Serverpod to Google Cloud Index (IDX) Platform

    I am writing to request the addition of Serverpod to the Google Cloud Index (IDX) platform. Serverpod is a robust backend framework designed specifically for Dart, leveraging the power of Flutter for its user interface. Given its features and compatibility with modern development practices, I believe it would be a valuable addition to the Google Cloud ecosystem.

    Key Features of… more

    2 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    1 comment  ·  Firebase Studio  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

16. Getting started Tutorials needs critical refinement and acurate articulation of label, navigation steps

    https://firebase.google.com/codelabs/firebase-nextjs#4
    Labels and directions in the tutorial are not matching the Firebase console. Configuration steps are vague and not descriptive enough. Example " Add your Firebase configuration to your web app code" section Step 2 makes sense if no app was build, but at this point of the tutorial the app has been created "My Nexst.js app", so these instruction are not right. Step 3 i believe is wrong or inaccurately written. Are we to transpose the contents to the npm tab from the "SDK setup and configuration pane" to the proper variable state or if we are to replace all the contents of the apphosting.yaml file with a variable and the objects from the npm or config. What does "In the file, replace the existing properties with those that you copied." mean....? Be specific, clear and detailed... This is waisting
    my time trying to figure out what you meant to write...

    https://firebase.google.com/codelabs/firebase-nextjs#4
    Labels and directions in the tutorial are not matching the Firebase console. Configuration steps are vague and not descriptive enough. Example " Add your Firebase configuration to your web app code" section Step 2 makes sense if no app was build, but at this point of the tutorial the app has been created "My Nexst.js app", so these instruction are not right. Step 3 i believe is wrong or inaccurately written. Are we to transpose the contents to the npm tab from the "SDK setup and configuration pane" to the proper variable state or if we are to replace… more

    2 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Other  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

17. Remote Config should be protected from man in the middle attacks

    Currently Remote Config can be sniffered and there is no option to configure protection from "man in the middle attacks" in client side.
    The best solution is to add support of Certificate Transparency.

    3 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Remote Config  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

18. Better google drive intergration

    In VS cell and other DEV environments i continually run into issues connecting to google drive AI and waste time in authorcatfication loops. So you have the chance to have better or even automatic integration with Google Drive, which would save so much time and make it easier to move data between different projects.

    1 vote

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Firebase Studio  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

19. Could you provide templates for NestJS?

    NestJS, celebrated for its modular architecture, has gained widespread acclaim in the TypeScript community. Many developers, myself included, opt for NestJS due to its robust features and development ease. Integrating NestJS templates into IDX projects would streamline development and attract a broader audience of TypeScript enthusiasts. I'm eager to see enhanced compatibility between NestJS and TypeScript-based templates.

    4 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Firebase Studio  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

20. I need a way in Google Cloud to redirect the public URL of jpeg files of my bucket to a Google Function endpoint for checking headers

    https://storage.googleapis.com/bucket/folder/file.jpg

    This is an example of a jpeg file in my Firebase Storage. A lot of websites are using my images illegally. I need a way to add a background check and process behind each access to the images... In PHP it is easy to do because the script can deliver the image, but here ? I don't know. I need a check on the headers of the website hosting the image, if the header referer is not OK, I want to redirect to an image saying that the real image is not available, or a 403

    3 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    1 comment  ·  Cloud Storage for Firebase  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating