Disable redirect for CID-in-subdomain even when X-Ipfs-Path is present #617
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 is a fix of a regression for #537 that was introduced when a redirect based on the presence of
X-Ipfs-Path
header support got added.Until we are able to provide the same origin-based security guarantees at a local gateway, we should not redirect resources that use cid-in-subdomain deployment (ipfs/in-web-browsers#89), as it is a strong hint they care about Origin-based isolation and we should not relax those guarantees.