-
Notifications
You must be signed in to change notification settings - Fork 29
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
Suborigins #66
Comments
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
As noted in ipfs/kubo#3209 (comment) Suborigin value must start with alpha:
Revisiting this in context of move to CIDv1 Base32 (https://github.com/ipfs/ipfs/issues/337) we probably should aim at normalizing to cidv1b32:
This is only for |
I believe it is time to close this to indicate that due to the lack of adoption (mozilla/standards-positions#31 (comment)) it is no longer a viable option for solving Origin isolation problem. Shifting focus to CID in Subdomains, which work today across all vendors: #89 |
Suborigins are WIP standard that – if implemented by browser vendors – could provide a way to isolate CID-specific paths into their own Origins.
It is an alternative way to solve the Problem of Inability to Control How Origin Is Calculated in Web Browsers (other one being CID-in-subdomain and programmable protocol handler API).
References
Notable Events
2014-11
public standards discussion announced @ lists.w3.org2015-01
ipfs/go-ipfs Implement per-page suborigins in the gateway2016-09
w3c/webappsec-suborigins: not allowed to start with number/can only start with letters2016-12
ipfs/go-ipfs: gateway: disable Suborigins as it conflicts the spec2017-09
Suborigins mozilla/standards-positions#31 (opened with a note about outstanding issues)2019-11
Suborigins mozilla/standards-positions#31 (comment) (closed due to no work)The text was updated successfully, but these errors were encountered: