Consider adding nosniff header to sensitive responses
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 1.8k
- Forks
- 717
- Avg merge
- 2d 6h
- Merged PRs (30d)
- 3
Description
In addition to the no-store header for potentially sensitive responses that was added in #10306 and #10628, there's also a new X-Content-Type-Options: nosniff header that is used by newly introduced cross-site reading functionality: https://chromium.googlesource.com/chromium/src/+/master/services/network/cross_origin_read_blocking_explainer.md
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 reviewing the implementations and tests associated with issues #10306 and #10628, then read the linked Chromium cross-site reading explanation. Identify which potentially sensitive responses already receive the no-store header and determine where nosniff should be applied. Done means the intended responses include X-Content-Type-Options: nosniff with tests covering the behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- security
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100