loading spec: Content sniffing prevention steps are missing in Parsing b3 algorithm
Open
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 1.3k
- Forks
- 125
- PR merge metrics
- No merged PRs in 30d
Description
#354 added two steps in the Parsing b2 CBOR headers algorithm:
- If responseHeaders does not contain
Content-Type, return a failure.- Set
X-Content-Type-Options/nosniffin responseHeaders.
But it did not add them into the Parsing b3 CBOR headers algorithm.
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 by comparing the linked Parsing b2 CBOR headers and Parsing b3 CBOR headers algorithms in loading.html. Confirm how b2 handles a missing Content-Type and sets X-Content-Type-Options/nosniff, then update the b3 specification so the missing steps are included. Done means the b3 algorithm documents both content-sniffing prevention steps.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 58/100