Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Disable redirect for CID-in-subdomain even when X-Ipfs-Path is present #617

Merged
merged 1 commit into from
Nov 12, 2018

Conversation

lidel
Copy link
Member

@lidel lidel commented Nov 12, 2018

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.

This is a fix of a regression for
#537
that was introduced when X-Ipfs-Path header support was 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, as it is a strong hint they care about
Origin-based isolation and we should not relax those guarantees.
@ghost ghost assigned lidel Nov 12, 2018
@ghost ghost added the status/in-progress In progress label Nov 12, 2018
@lidel lidel merged commit 458bf34 into master Nov 12, 2018
@ghost ghost removed the status/in-progress In progress label Nov 12, 2018
@lidel lidel deleted the fix/redir-cid-in-subdomain branch November 12, 2018 15:50
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant