Allowable HTTP status code for Bundle?
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 1.3k
- Forks
- 125
- PR merge metrics
- No merged PRs in 30d
Description
Currently, file formats just expect the status code should be exactly 3 ASCII decimal digits.
But for SignedExchanges, the "Loading Signed Exchanges" spec allows only 200 for the status code (https://wicg.github.io/webpackage/loading.html#parse-cbor-headers step 2).
Probably, BundledExchanges also needs a similar restriction, but probably we want range requests and redirects work (206, 307, 308).
For Chrome implementation, we will start from just allowing only 200 for the initial experimental implementation, but will support others if we want.
crbug.com/990733 tracks the Chrome side implementation.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the issue's "Loading Signed Exchanges" specification link and compare its status-code rule with the current Bundle and Bundled Exchanges format requirements. Review crbug.com/990733 for the related Chrome implementation context. Done means reaching a decision on which status codes Bundled Exchanges should allow and documenting that restriction clearly.
Written by the indexing model from the issue text.
Assessment
- Domain
- web-dev
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100