-
-
Notifications
You must be signed in to change notification settings - Fork 3k
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
Serve Trustless IPFS HTTP Gateway API via libp2p (experimental) #10049
Labels
kind/feature
A new feature
Comments
2023-08-29 conversation on testing this: |
This was referenced Aug 29, 2023
Closed
BigLep
changed the title
Serve Trustless IPFS HTTP Gateway API via libp2p
Serve Trustless IPFS HTTP Gateway API via libp2p (experimental)
Sep 7, 2023
6 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Description
The trustless gateway specification allows retrieval of blocks and certain types of DAGs over HTTP.
Some tooling has already been built that leverages the trustless gateway API to move data around (https:/little-bear-labs/ipfs-chromium, https:/ipfs/bifrost-gateway, https:/filecoin-project/lassie, helia-enabled service worker, etc.).
While some of these tools use HTTP itself, it would also be nice if they could use the same semantics but without the requirements of CA certs (+ domain names), public IP addresses, etc. To enable this we can use HTTP over libp2p.
This proposal is to start by enabling an optional server for Trustless Gateway over libp2p, and future issues may tackle support for client support as well.
The relevant pieces are:
.well-known
support, etc.)Experimental.P2pHttpProxy
featureGateway.NoFetch=true
(only return blocks that are in local repo and 5XX (502?) for the rest?)The text was updated successfully, but these errors were encountered: