Add examples for X-Content-Type-Options header #1844
Draft
+47
−0
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add examples for X-Content-Type-Options header Addresses issue [whatwg#636](whatwg#636) by adding comprehensive examples to the 'Should response to request be blocked due to nosniff?' algorithm. The examples clarify: - When responses are blocked (MIME type mismatch, missing Content-Type) - When responses are allowed (correct MIME type, no X-Content-Type-Options header) - Different request destinations (script, style, image) This should help web developers and implementers understand the exact behavior of the X-Content-Type-Options: nosniff directive.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Add examples for X-Content-Type-Options header
This is an editorial change that adds comprehensive examples to clarify the behavior of the X-Content-Type-Options: nosniff directive, addressing issue #636.
The examples illustrate when responses are blocked vs allowed, helping web developers and implementers understand the algorithm's behavior without changing any normative requirements.
Fixes #636
Preview | Diff