Add 'json' as a value for Sec-Fetch-Dest #42160
Merged
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
github-actions
bot
added
Content:HTTP
Contributor
|
Preview URLs Flaws (3)URL:
|
wbamberg
approved these changes
Nov 29, 2025
estelle
pushed a commit
that referenced
this pull request
Dec 1, 2025
Add 'json' as a value for sec-fetch-dest
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Description
The docs for the Sec-Fetch-Dest header were missing the valid value
json. This fixes adds it.I wasn't totally sure how best to link to the docs for JSON imports. I did something which works but if there's a better way feel free to push it up.
Motivation
Match spec.
Additional details
See fetch spec for request destinations, and fetch metadata spec for the bit which says that this is reflected in the Sec-Fetch-Dest header.
Related issues and pull requests
None that I could find.