W3C home > Mailing lists > Public > ietf-http-wg@w3.org > July to September 2010

Re: NEW: value space of status codes [#213]

From: Mark Nottingham <mnot@mnot.net>
Date: Thu, 8 Jul 2010 08:43:31 +1000
Cc: HTTP Working Group <ietf-http-wg@w3.org>
Message-Id: <FD5B15AB-5DB4-4FEE-860F-A1DE60DAA1EE@mnot.net>
To: Julian Reschke <julian.reschke@gmx.de>
See also

Do we need a space (e.g., 0xx) for private use?

On 30/06/2010, at 3:34 AM, Julian Reschke wrote:

> On 29.06.2010 19:05, Mark Nottingham wrote:
>> p1 defines HTTP status codes as "a 3-digit integer result code" with the following value space:
>> The first digit of the Status-Code defines the class of response. The last two digits do not have any categorization role. There are 5 values for the first digit:
>> 	 1xx: Informational - Request received, continuing process
>> 	 2xx: Success - The action was successfully received, understood, and accepted
>> 	 3xx: Redirection - Further action must be taken in order to complete the request
>> 	 4xx: Client Error - The request contains bad syntax or cannot be fulfilled
>> 	 5xx: Server Error - The server failed to fulfill an apparently valid request
>> The BNF, however, allows other values;
>> Status-Code = 3DIGIT
> One might consider "3DIGIT" as a rule for parsers (thus, in P1), and the first digits as a semantical constraint (thus, P2).
>> IANA has asked what the status of codes is outside of this range; e.g., is a 0xx status code reserved, unregistered, or just not allowed? Likewise for 6xx (used by some implementations for local status codes) and upwards.
> Not allowed in HTTP/1.1.
>> Also, should the value space be defined in p1 or p2?
> In P2, IMHO. Maybe move part of P1, Section 5.1.1 into P2, Section 4?
> Best regards, Julian

Mark Nottingham     http://www.mnot.net/
Received on Wednesday, 7 July 2010 22:44:04 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 17:13:47 UTC