You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Users need to know how to convert HTTP gateway URLS to ipfs:// and ipns:// to be able to benefit from verifiable retrieval. This is error-prone, and encourages people to reinvent conversion code over and over again.
First user of this feature will be service worker gateway, which needs {redirect:'manual'} to return meaningful redirect as a fix for ipfs/service-worker-gateway#62
The text was updated successfully, but these errors were encountered:
Current state
Users need to know how to convert HTTP gateway URLS to
ipfs://
andipns://
to be able to benefit from verifiable retrieval. This is error-prone, and encourages people to reinvent conversion code over and over again.Feature request
It should be possible to pass http(s):// URLs that follow either path gateway or subdomain gateway spec, or single DNSLink name gateway, and get verified
Response
back for relevant /ipns or /ipfs content path.First user of this feature will be service worker gateway, which needs
{redirect:'manual'}
to return meaningful redirect as a fix for ipfs/service-worker-gateway#62The text was updated successfully, but these errors were encountered: