feat: gateway with dedicated cf gateway #1546
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
vasco-santos
force-pushed
the
feat/gateway-with-dedicated-cf-gateway
branch
from
0e520c3 to
96a576c
Compare
Deploying with
|
| Latest commit: |
16f2d4e
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://c5c17dc5.nft-storage-1at.pages.dev |
vasco-santos
commented
Mar 10, 2022
Co-authored-by: Alan Shaw <alan.shaw@protocol.ai>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR adds our dedicated CF gateway as the gateway to be used 🎉
I had our dedicated CF gateway
cf.nftstorage.linksetup with Cloudflare team, this will be an offering from them in the future and we had a manual process with them to have the DNS setup and proxying to ipfs.cloudflare.com.With this dedicated gateway we have more freedom and powers with custom rate limits. With this in mind, a set of rules were put in place to avoid abuse and hammering this domain:
cf.nftstorage.link/*from the outside world (only our worker can access it, same CF zone ID)cf.nftstorage.link/*perX-Forwarded-Forcf-connecting-ipinstead, given clients can easily manipulateX-Forwarded-Forto add fake proxies just to circumvent limits. If so, we will need to add a new header to the request to the gateways to use it. Thoughts?Closes #1195