2 ms·
We're planning to use Same-origin policy to prevent this. It was first brought up here: https://github.com/ipfs/go-ipfs/issues/651 https://github.com/ipfs/go-ip
by diggan 10y ago
We're planning to use Same-origin policy to prevent this. It was first brought up here: https://github.com/ipfs/go-ipfs/issues/651 https://github.com/ipfs/go-ipfs/issues/651
You can read more about same-origin policy here:
https://developer.mozilla.org/en-US/docs/Web/Security/Same-origin_policy https://developer.mozilla.org/en-US/docs/Web/Security/Same-o...
- 0xcde4c3db 10y agoPutting a hash in the hostname/domain would also be using same-origin policy. The issue you linked refers to using suborigins, which seems to still be a draft proposal with no implementer buy-in outside of Chromium [1]. [1] https://bugzilla.mozilla.org/show_bug.cgi?id=1231225 https://bugzilla.mozilla.org/show_bug.cgi?id=1231225