Skip to content

Commit

Permalink
Remove speculation and discouraging language about usage
Browse files Browse the repository at this point in the history
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.
  • Loading branch information
stevecrozz committed Apr 25, 2024
1 parent 3f70090 commit 6b4783b
Showing 1 changed file with 0 additions and 5 deletions.
5 changes: 0 additions & 5 deletions files/en-us/web/http/status/406/index.md
Original file line number Diff line number Diff line change
Expand Up @@ -18,11 +18,6 @@ Proactive content negotiation headers include:
- {{HTTPHeader("Accept-Encoding")}}
- {{HTTPHeader("Accept-Language")}}

In practice, this error is very rarely used. Instead of responding using this error
code, which would be cryptic for the end user and difficult to fix, servers ignore the
relevant header and serve an actual page to the user. It is assumed that even if the
user won't be completely happy, they will prefer this to an error code.

If a server returns such an error status, the body of the message should contain the
list of the available representations of the resources, allowing the user to choose
among them.
Expand Down

0 comments on commit 6b4783b

Please sign in to comment.