36 results found
-
Trusted headers for client IP address via Firebase Hosting
Context: from a backend running on Cloud Run/Cloud Functions, how to determine client IP address, when you need to TRUST it for IP-address based access restrictions.
You can normally find the real client IP as the first entry in the X-Forwarded-For header, but you cannot trust it.
If you are using Cloud Run (or Cloud Functions gen 2), then as far as I can tell the Cloud Run orchestrator always sits as a proxy in front of your container. This means you can trust the last entry in X-Forwarded-For as this is the client IP seen by Cloud Run itself.…
3 votes -
Allow URLs to be accessible fully, or by invitation, or by password protection, like Notion and Figma
Allow natively what we can do in Notion / Figma (sharing a prototype), by sharing a page with the followings options:
1/ allow a page to be fully accessible (that's already possible, so the default)
2/ allow a page to be viewed only if we provide another User a link.
3/ allow a page to be viewed if 2/ + password protected10 votes -
17 votes
-
Remix support
Have out of the box support for Remix framework implementing SSR which also work with the Emulators.
3 votes -
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 -
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 -
15 votes
-
39 votes
-
12 votes
-
12 votes
-
5 votes
-
2 votes
-
25 votes
-
4 votes
-
6 votes
-
3 votes
- Don't see your idea?