Repository navigation
fix: route ipfs lookups through the production proxy only - #19
Merged
Merged
Conversation
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Public IPFS gateways are unreliable from residential networks (429 service-worker-only, multi-second hangs) — every token icon/metadata load paid a multi-second dead-gateway walk, and flaky egress could kill the final hop, leaving 502s and letter-avatar fallbacks.
The /ipfs/ same-origin proxy now defaults to the project's production bridge proxy only (R2-backed, content-addressed, measured <1s). The gateway list stays env-overridable via IPFS_GATEWAY_URLS and the failover loop remains for operator-added mirrors. New test covers the honest 502 when the only proxy is down.