Serve Trustless IPFS HTTP Gateway API via libp2p (non-experimental) #10118
Description
Checklist
- My issue is specific & actionable.
- I am not suggesting a protocol enhancement.
- I have searched on the issue tracker for my issue.
Description
While adding server-side support as an experimental feature was added in #10049 we'd like to get this to the point where it's both non-experimental and enabled by default.
This is a tracking issue for what needs to happen.
Some of the requirements:
- Needs more people to use and report on how well it works
- In particular this means that some well deployed clients are able to use this feature well and are benefitting from it and that there's been some time for bug reports, missing features, etc. to come in and be resolved
- Needs UX work for handling shared configurations of the HTTP over TCP and HTTP over libp2p endpoints
- For example, making it simpler to share configuration for the non-recursive "HTTP transport" (i.e. NoFetch = true)
- Needs a mechanism for HTTP handler to signal supported features (IPIP-425)
- While not strictly necessary for basic operation, not having this makes designing clients that leverage fetching data from multiple peers painful