Added example for X-Content-Type-Options in Fetch Standard #1809
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.
Summary
This PR adds an example demonstrating how to use the
X-Content-Type-Options
HTTP header with the Fetch API.Why This Change?
X-Content-Type-Options
header prevents MIME-type sniffing, improving web security.Changes Made
<pre class="example">
block with a Fetch API usage example.id="example-x-content-type-options"
for Bikeshed validation.Checklist (N/A for This PR)
Since this is an editorial change, some checklist items are not applicable:
This PR is purely editorial, and no implementation changes are needed. Happy to adjust if maintainers have feedback! 🚀
Preview | Diff