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

Re: draft-yevstifeyev-http-headers-not-recognized-01.txt

From: Sylvain Hellegouarch <sh@defuze.org>
Date: Tue, 23 Nov 2010 11:37:33 +0100
Message-ID: <AANLkTik-0iuKUOhqr_wDy9zVZY89Dvbj-XSg09CMkbf-@mail.gmail.com>
To: Julian Reschke <julian.reschke@gmx.de>
Cc: Mykyta Yevstifeyev <evnikita2@gmail.com>, ietf-http-wg@w3.org
On Tue, Nov 23, 2010 at 11:13 AM, Julian Reschke <julian.reschke@gmx.de>wrote:

> On 23.11.2010 10:16, Mykyta Yevstifeyev wrote:
>
>> ...
>>
>> If a server sends 4xx code, it stops procesing the request.
>> Generally unrecognized headers are not critical - all
>> 'vital' headers MUST be supported by servers. If a client receives
>> such a response, it SHOULD avoid sending requests
>> with mentioned headers while server MUST cntinue processing
>> the request.
>> ...
>>
>
> *Why* "SHOULD" it avoid sending those? What's the problem you're trying to
> solve? Wasted bits? It would be helpful to understan
>
>
Also I'm afraid we'd end up with a ping/pong game where clients would likely
dismiss the new status code anyway as servers ignore currently headers they
don't understand.

-- 
- Sylvain
http://www.defuze.org
http://twitter.com/lawouach
Received on Tuesday, 23 November 2010 10:38:12 GMT

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