SOMEGUY_HTTP_BLOCK_PROVIDER_ENDPOINTS as routing proxy for trustless gateways #109
Labels
help wanted
Extra attention is needed
kind/enhancement
A net-new feature or improvement to an existing feature
P2
Medium: Good to have, but can wait until someone steps up
Summary
Allow someguy to act as delegated router for trustless gateway endpoints that don't have own
/routing/v1/providers/{cid}
(by probing the statically configured endpoint).Value for ecosystem
Simplify integration of existing storage systems (e.g. ipfs-cluster's Kubo nodes running NoFetch gateway, or simpler hosting like S3 buckets hosting static blocks) into everything that accepts addictional delegated routing endpoints (boxo/helia, kubo/rainbow, inbrowser.link/verified-fetch).
Potentially helps with:
Implementation
Add
SOMEGUY_HTTP_BLOCK_PROVIDER_ENDPOINTS
that accepts list of gateway origins, similar to how existingSOMEGUY_PROVIDER_ENDPOINTS
works.The difference is that the way those endpoints are queried, is
HEAD /ipfs/cid?format=raw
withAccept: application/vnd.ipld.raw
, and if result of the probe was HTTP 200 (OK), then apeer
results with/tls/http
multiaddr is returned.When
SOMEGUY_HTTP_BLOCK_PROVIDER_ENDPOINTS
are defined, use them in addition to other routing systems when returning results for/routing/v1/providers/{cid}
.The text was updated successfully, but these errors were encountered: