W3C home > Mailing lists > Public > ietf-http-wg@w3.org > April to June 2009

RE: i37: Vary and non-existant headers

From: Brian Smith <brian@briansmith.org>
Date: Wed, 6 May 2009 10:10:09 -0500
To: "'Yves Lafon'" <ylafon@w3.org>, "'Mark Nottingham'" <mnot@mnot.net>
Cc: "'Julian Reschke'" <julian.reschke@gmx.de>, "'HTTP Working Group'" <ietf-http-wg@w3.org>
Message-ID: <007d01c9ce5c$c14c5c90$43e515b0$@org>
Yves Lafon wrote:
> How about:
> "Implementations might define header matching as the equivalence of
> their internal representations".

That looks like "Header matching is implementation-defined."

It makes sense that transparent proxies must use character-by-character
comparison (no canonicalization). Non-transparent proxies are already free
to rewrite the "Accept-Encoding" header of requests, so they are free to do
whatever canonicalization they want (RFC 2616 section 13.5.2), AFAICT. That
is, a proxy cache that treats "Accept-Encoding: inflate, identity" the same
as "Accept-Encoding: inflate" is the same as a non-transparent proxy cache
that rewrites "Accept-Encoding: inflate, identity" to "Accept-Encoding:
inflate". Such a cache can't claim to be transparent (because it isn't).

- Brian 
Received on Wednesday, 6 May 2009 15:10:51 GMT

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