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

Re: HTTPbis -10 drafts published : Connection header

From: Roy T. Fielding <fielding@gbiv.com>
Date: Wed, 14 Jul 2010 19:53:37 -0700
Cc: HTTP Working Group <ietf-http-wg@w3.org>
Message-Id: <AAC78FC2-4A6D-4EB4-B81B-C574AE796E00@gbiv.com>
To: Adrien de Croy <adrien@qbik.com>
On Jul 14, 2010, at 6:50 PM, Adrien de Croy wrote:

> ok, but what about from RFC2616 S 14.10
> 
>   Message headers listed in the Connection header MUST NOT include end-
>   to-end headers, such as Cache-Control.
> 
> 
> there are only 4 types of header (AFAICT)
> 
> general-header
> request-header
> response-header
> entity-header
> 
> any unknown header is an extension header, and is treated as an entity header.

No.  It is parsed as an entity-header.

> All entity headers are end to end are they not?

Anything in the spec that says something is end-to-end or
hop-by-hop will be rewritten soon.  Fields are hop-by-hop
when they are listed in Connection (or are Connection).
All others are end-to-end.

> Therefore it's illegal to specify any entity header in the Connection header.

That does not change how they are handled.

....Roy
Received on Thursday, 15 July 2010 02:54:08 GMT

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