gateway: evaluate switching back to standard http library
Open
help wanted
need/analysis
P2
topic/gateway
- Dominant language
- Go
- Stars
- 316
- Forks
- 163
- Avg merge
- 4d 12h
- Merged PRs (30d)
- 8
Description
`boxo/gateway` uses custom (forked) implementation of [`http.ServeContent`](https://pkg.go.dev/net/http#ServeContent), the code is in [`boxo/gateway/erve_http_content.go#httpServeContent`](https://github.com/ipfs/boxo/blob/1ef7a48b4c0fe6740b867f806d0c8273bfa39f4b/gateway/serve_http_content.go#L47)
TLDR: we forked it in 2023 for _reasons_ (afaik to facilitate streaming CARs?) but created surface for bugs:
- Ref. https://github.com/ipfs/boxo/pull/922
May be good time to re-evaluate if it is cost-effective / feasible to switch back.
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.