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

Support http(s):// gateway URLs #11

Closed
Tracked by #31
lidel opened this issue Mar 4, 2024 · 1 comment
Closed
Tracked by #31

Support http(s):// gateway URLs #11

lidel opened this issue Mar 4, 2024 · 1 comment

Comments

@lidel
Copy link
Member

lidel commented Mar 4, 2024

Current state

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.

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#62

@achingbrain
Copy link
Member

I think this has been implemented by #4

@SgtPooki SgtPooki closed this as completed Mar 7, 2024
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

No branches or pull requests

3 participants