W3C home > Mailing lists > Public > ietf-http-wg@w3.org > January to March 2008

RE: Unknown and misplaced headers as entity headers

From: Henrik Nordstrom <henrik@henriknordstrom.net>
Date: Fri, 14 Mar 2008 00:20:39 +0100
To: Brian Smith <brian@briansmith.org>
Cc: "'HTTP Working Group'" <ietf-http-wg@w3.org>
Message-Id: <1205450439.10356.83.camel@HenrikLaptop>

On Wed, 2008-02-27 at 05:17 -0800, Brian Smith wrote:
> What problem does this cause? When an HTTP application encounters an
> unknown header, that header would still be a request-header,
> response-header, entity-header, or general-header. The only difference
> would be that the specification doesn't try to dictate how the
> application classifies it. 

It's very important for caches to never wrongly classify an entity
header as one of the other classes as doing so may result in loss of the
header. As it's not possible to know what an unknown extension header
should be classified as the safe default is entity header unless
indicated otherwise using Connect.

Received on Thursday, 13 March 2008 23:21:50 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 1 March 2016 11:10:45 UTC