Talk:List of HTTP status codes
This is the talk page for discussing improvements to the List of HTTP status codes article. This is not a forum for general discussion of the article's subject. |
Article policies
|
Find sources: Google (books · news · scholar · free images · WP refs) · FENS · JSTOR · TWL |
Archives: 1, 2, 3, 4, 5, 6Auto-archiving period: 30 days |
Template:Friendly search suggestions
This article has not yet been rated on Wikipedia's content assessment scale. It is of interest to the following WikiProjects: | |||||||||||||||||||||
Please add the quality rating to the {{WikiProject banner shell}} template instead of this project banner. See WP:PIQA for details.
Please add the quality rating to the {{WikiProject banner shell}} template instead of this project banner. See WP:PIQA for details.
|
This is the talk page for discussing improvements to the List of HTTP status codes article. This is not a forum for general discussion of the article's subject. |
Article policies
|
Find sources: Google (books · news · scholar · free images · WP refs) · FENS · JSTOR · TWL |
Archives: 1, 2, 3, 4, 5, 6Auto-archiving period: 30 days |
Decimal codes?
Is there an http error code with a decimal code? I thought i once saw a slashdoted webpage display something like:
5xx.x - too many clients connected to server try again later Microsoft internet services ver x ( or whatever ms calls their webserver
this was a while ago so i'm not sure if i remeber this right, but i was just wondering. Bawolff 05:13, 8 Mar 2005 (UTC)
- RFC 1945 defines the response line as follows.
- Status-Line = HTTP-Version SP Status-Code SP Reason-Phrase CRLF
- The Status-Code element is a 3-digit integer result code of the attempt to understand and satisfy the request. The Reason-Phrase is intended to give a short textual description of the Status-Code. The Status-Code is intended for use by automata and the Reason-Phrase is intended for the human user. The client is not required to examine or display the Reason-Phrase.
- So no, there's no decimal code. The status code is used by the client to take an action, e.g. prompt for a password, re-fetch from a different location, etc. If a server output a dodgy code it would confuse the client, though it's worth remembering that what you see in the client is usually a HTML page generated by the server and is part of the body of the response – which doesn't necessarily contain the same status information as it gives to the client in the header.
- — Lee J Haywood 19:59, 8 Mar 2005 (UTC)
okay. I was just wondering because I thought I saw on once. Bawolff 23:49, 9 Mar 2005 (UTC)
- IIS has different ways of handling the same error depending on how it was caused. It returns the correct status code to the user, however, its default error pages also have sub-codes for explaining the particular circumstances behind an error. While there are numerous 401.x or 403.x pages, officially they are all classed as their respective main class. Chris 00:36, 26 Mar 2005 (UTC)
Sample header for every status code?
just like in Hypertext_Transfer_Protocol#Sample
Maybe just a link to a page of samples? Anyone know of one? If I find them, would it be good to add them?
nginx
The article previously made the following claim but, in fact, you are able to specify an error_page for errors 495 and 495. Failing this configuration, a default error page is returned.
These are only used for logging purposes, no actual response is sent with these codes.
tus
The tus protocol (https://tus.io/) defines a few extra status codes. Should we add them?