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

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

From: Julian Reschke <julian.reschke@gmx.de>
Date: Thu, 08 Jul 2010 11:37:41 +0200
Message-ID: <4C359C65.8050800@gmx.de>
To: Willy Tarreau <w@1wt.eu>
CC: Mark Nottingham <mnot@mnot.net>, "Roy T. Fielding" <fielding@gbiv.com>, HTTP Working Group <ietf-http-wg@w3.org>
On 08.07.2010 11:03, Willy Tarreau wrote:
> On Thu, Jul 08, 2010 at 10:57:05AM +0200, Julian Reschke wrote:
>> On 08.07.2010 02:13, Mark Nottingham wrote:
>>> That's roughly what I mean by private use -- i.e., don't ever serialise on the wire.
>>
>> If it's never on the wire, do we really care?
>>
>> If APIs need a value range that is guaranteed to be never used in
>> HTTP/1.1, simply pick values that can't be put on the wire, such as<
>> 0 or>  999.
>
> or maybe simply add the precision that codes<  100 and>= 600 will never
> be emitted over the wire ?

I really don't see the benefit. Maybe we want to use them in HTTP/1.2?

What's wrong with < 0 or > 999?

Best regards, Julian
Received on Thursday, 8 July 2010 09:38:19 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Friday, 27 April 2012 06:51:23 GMT