Remove speculation and discouraging language about usage #33270
Merged
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
|
Preview URLs (comment last updated: 2024-06-17 06:09:39) |
There's nothing wrong with using HTTP response code 406. This code is the correct and appropriate one to use for its purpose. We should not be discouraging people from using it with this kind of language.
sideshowbarker
approved these changes
Jun 17, 2024
|
Steve, thanks much, and congrats on landing your first docs change here — welcome aboard 🎉 |
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.
There's nothing wrong with using HTTP response code 406. This code is the correct and appropriate one to use for its purpose. We should not be discouraging people from using it with this kind of language.
Motivation
The existing language puts a negative framing around HTTP 406 and also makes claims about how widespread the use of this status code is. It is very commonly used in for HTTP APIs and I'm sure it is used at least on occasion for human clients too. Are we able to support this claim? It also says "servers ignore" this header (maybe referring to Accept)? This all seems like pretty strange language to have in MDN.