53 results found

1. The ability to turn on/off the decoding of encoded data url in firebase.json

   When I hosted a frontend client (React JS) and backend (NodeJS) server in hosting and functions combination, there were some scenarios where in I needed to send data (to server) which contained slash (so encoded them).

   This was where the problem rose, the encoded component was automatically decoded by the firebase hosting itself and sent the wrong url to the underlying server.

   Therefore firebase should give us the ability to turn on/off the decoding of encoded data url in firebase.json

   my current firebase.json file -

   {
   "functions": [
   {
   "source": "functions",
   "codebase": "default",
   "ignore": [
   "nodemodules",
   ".git",
   "firebase-debug.log",
   "firebase-debug..log"
   ]
   }
   ],
   "hosting": {
   "public": "/functions/public",
   "ignore": [
   "firebase.json",
   "/.",
   "**/nodemodules/"
   ],
   "rewrites": [
   {
   "source": "",
   "function": "app"
   }
   ]
   }
   }

   When I hosted a frontend client (React JS) and backend (NodeJS) server in hosting and functions combination, there were some scenarios where in I needed to send data (to server) which contained slash (so encoded them).

   This was where the problem rose, the encoded component was automatically decoded by the firebase hosting itself and sent the wrong url to the underlying server.

   Therefore firebase should give us the ability to turn on/off the decoding of encoded data url in firebase.json

   my current firebase.json file -

   {
   "functions": [
   {
   "source": "functions",
   "codebase": "default",
   "ignore": [
   "nodemodules",
   ".git",
   "firebase-debug.log",
   "firebase-debug.… 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  ·  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

2. Remix support

   Have out of the box support for Remix framework implementing SSR which also work with the Emulators.

   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  ·  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

3. The Firebase target apply command has also to update the firebase.json with the target name!

   The Firebase target apply command has also to update the firebase.json with the target name!

   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  ·  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

4. Some Hosting Feedback
   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  ·  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. allow app hosting without a cloud billing account

   Firebase app hosting without a cloud billing account should be possible.
   Also to have a custom subdomain for the app url.
   Most people use Google and other tools without any billing account. So there is a high potential of firebase users for this feature. Also to simplify to publish the app without needing to know how CLI works within the firebase studio.

   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  ·  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

6. Add a CLI flag for hosting project previous release count option

   I have an ecommerce SAAS company where each client/tenant website is hosted on Firebase Hosting. We have over 80 websites hosted across six Firebase projects.

   We create each new site using the Firebase CLI:

   firebase hosting:sites:create [options] <siteId>

   The only options for this command are:

   --app <appId> specify an existing Firebase Web App ID
   -h, --help display help for command

   I'd like to request an additional option to set the "previous releases to keep", aka "previous release count".

   After I create a new site, I have to deploy the new website to Firebase hosting before I can set the previous release count on the Firebase Hosting website. The website won't let me set the release count before deploying my first release.

   If I can set this previous release count when creating the site, then I don't have to wait until after I complete these two required steps (plus remember to do it).

   If I forget to set the previous release count, then I'll end up with too many previous releases that I'm paying for that I'll never use.

   Basically, this would eliminate one of the many little annoying steps I need to do manually when launching a new tenant website.

   I have an ecommerce SAAS company where each client/tenant website is hosted on Firebase Hosting. We have over 80 websites hosted across six Firebase projects.

   We create each new site using the Firebase CLI:

   firebase hosting:sites:create [options] <siteId>

   The only options for this command are:

   --app <appId> specify an existing Firebase Web App ID
   -h, --help display help for command

   I'd like to request an additional option to set the "previous releases to keep", aka "previous release count".

   After I create a new site, I have to deploy the new website to Firebase hosting before I can set the previous… 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  ·  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

7. Support for Proper 404 Status Codes and Multiple 404 Pages Based on URL Patterns on Firebase Hosting

   Currently, when using a custom 404 page (e.g., 404.html), Firebase Hosting always responds with a 200 status code, even when the page is served via a rewrite rule.
   This differs from behavior on traditional servers (e.g., Nginx with the internal directive), where the server can correctly return a 404 while still serving a custom error page.

   Why this matters:
   - Proper HTTP status codes are essential for SEO.
   - Search engines may incorrectly index 404 pages if they return 200.
   - Client applications and monitoring tools rely on correct status codes.

   Additionally, In many multilingual or multi-section sites, different parts of a website require different 404 pages.
   At the moment, the only workaround is to use rewrite rules, such as:

   {
     "rewrites": [
       { "source": "/es/**", "destination": "/es/404.html" }
     ]
   }
   

   However, this still returns 200 instead of 404, which causes the same issue as above.

   Requested enhancement:
   - Allow developers to define multiple 404 handlers depending on URL patterns (e.g. /es/** → /es/404.html, /fr/** → /fr/404.html)
   - Ensure each of these handlers can return a real 404 status code

   These two capabilities would significantly improve:
   - SEO accuracy
   - Error analytics
   - User experience for multilingual or multi-section websites
   - Parity with traditional server behavior

   Thank you for considering these enhancements!

   Currently, when using a custom 404 page (e.g., 404.html), Firebase Hosting always responds with a 200 status code, even when the page is served via a rewrite rule.
   This differs from behavior on traditional servers (e.g., Nginx with the internal directive), where the server can correctly return a 404 while still serving a custom error page.

   Why this matters:
   - Proper HTTP status codes are essential for SEO.
   - Search engines may incorrectly index 404 pages if they return 200.
   - Client applications and monitoring tools rely on correct status codes.

   Additionally, In many multilingual or multi-section sites, different parts… 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  ·  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. Add windows...
   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  ·  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

9. Updates ESLint to V9

   The current version of ESLInt is V8 - Update it to V9

   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  ·  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. AAAA/IPv6 DNS records
    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  ·  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

11. Enable deployments that don't delete previous artifacts

    Have an option to deploy and keep previous deployment artifacts instead of deleting them.

    Even better would be an option for this with a TTL on previous deployment artifacts (that haven't been updated or re-deployed in subsequent deployments).

    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  ·  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

12. Site Not Found

    i have deployed and when i try to go on default site i see site not found

    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  ·  Hosting  ·  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

13. Add ability to set release version.

    Right now we can not control version. After deploy version at api looks like this:
    "sites/<site_name>/versions/2e65a07a8886cdb4"

    I want to be able to provide my own string (git hashtag, semver, etc). It requires to match source code and deployed version. The version should be shown at UI and we should be able to rollback based on this version. During deploy with the same version CLI should throw error.

    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  ·  Hosting  ·  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