Content routing hint via HTTP headers
Open
kind/feature
topic/gateway
- Dominant language
- Go
- Stars
- 17.1k
- Forks
- 3.2k
- Avg merge
- 3d 18h
- Merged PRs (30d)
- 11
Description
Came up in https://github.com/ipfs/go-ipfs/issues/6383#issuecomment-511645397.
The HTTP gateway could read a (series of) `IPFS-Provider: /some/multiaddr` hint(s) and use them to inform content routing decisions when trying to find the content in question.
This could be useful for (d)apps that have known stable providers. IPFS would/could still look elsewhere, this would just allow dapps to provide a known-good fallback.
Contributor guide
Assessment
This issue has not been assessed yet.