HTTP Header template - add case if no browser compat applies #36298
+10
−1
Conversation
This file contains 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
hamishwillee
requested review from
chrisdavidmills
and removed request for
a team
github-actions
bot
added
Content:Meta
Josh-Cena
reviewed
Oct 12, 2024
| @@ -44,6 +44,9 @@ page-type: mdn-writing-guide | |||
| > Note that you may first need to create/update an entry for the HTTP header in our <a href="https://github.com/mdn/browser-compat-data">Browser compat data repo</a>, and the entry for the header will need to include specification information. | |||
| > See our [guide on how to do this](/en-US/docs/MDN/Writing_guidelines/Page_structures/Compatibility_tables). | |||
| > | |||
| > Browser compatibility does not apply for HTTP headers where no specific implementation is provided (such as automatically adding a request header to some requests or changing behaviour based on data in a response header). | |||
There was a problem hiding this comment.
Suggested change
| > Browser compatibility does not apply for HTTP headers where no specific implementation is provided (such as automatically adding a request header to some requests or changing behaviour based on data in a response header). | |
| > Browser compatibility does not apply for HTTP headers where no specific implementation is provided (such as automatically adding a request header to some requests or changing behavior based on data in a response header). |
"Stupid Americanish," I hear you say.
| _If the browser has specific handling for the header, remove the text below:_ | ||
|
|
||
| This header has no specification-defined browser integration ("browser compatibility" does not apply). | ||
| Developers can set and get HTTP headers using `fetch()` in order to provide application-specific implementation behavior. |
There was a problem hiding this comment.
I feel like this is a bit too specific. I know the last PR used this verbiage but IMO HTTP is not confined to JS-server communication. What about non-JS HTTP clients?
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.
For many HTTP headers there is no specific browser integration - i.e. the browser itself doesn't do anything to add headers to requests or handle them in responses (you can write your own code to do this using
fetch().For this case there is no browser compatibility. To make it clear that this is intentional we can add some standard text to the browser compatibility section. This proposes said text.
Falls out of discussion in #36197