search

ipfs / in-web-browsers

Tracking the endeavor towards getting web browsers to natively support IPFS and content-addressing
https://docs.ipfs.tech/how-to/address-ipfs-on-web/
MIT License
349 stars 29 forks source link

Endpoint for redirect-based navigator.registerProtocolHandler #168

Closed lidel closed 1 year ago

lidel commented 4 years ago

ipfs:// URI support landed in Chromium:

For the time being registerProtocolHandler is limited to redirect-based handler, but its still exciting.

Idea: add Gateway endpoint that translates URI to IPFS content path: 

https://dweb.link/ipfs/?uri=%s
HTTP GET → https://dweb.link/ipfs/?uri=ipfs%3A%2F%2Fbafybeigdyrzt5sfp7udm7hu76uh7y26nf3efuylqabf3oclgtqy55fbzdi
   → HTTP 301 → https://dweb.link/ipfs/bafybeigdyrzt5sfp7udm7hu76uh7y26nf3efuylqabf3oclgtqy55fbzdi
lidel commented 3 years ago

/ipfs/?uri= was implemented in https://github.com/ipfs/go-ipfs/pull/7802 and is already live at dweb.link Remaining work here is to document the endpoint after go-ipfs 0.8.0 ships and switch Companion to it.

olizilla commented 3 years ago

Noting here as well, Firefox no longer supports calling registerProtocolHandler with ipfs as the scheme. https://github.com/arewedistributedyet/arewedistributedyet/issues/23#issuecomment-824833125

Nudging is occuring in bugzilla https://bugzilla.mozilla.org/show_bug.cgi?id=1631446

lidel commented 1 year ago

Small update based on Chromium bug 64100: New Extension API: protocol_handlers and https://github.com/w3c/webextensions/issues/317:

lidel commented 1 year ago

This is now part of subdomain specs (which provides Origin per root CID):