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

Re: Making Implicit C-E work.

From: Matthew Kerwin <matthew@kerwin.net.au>
Date: Sat, 3 May 2014 15:57:29 +1000
Message-ID: <CACweHND2HA8xyJ1uir8fm+v+mW3vR=+z8vx3mKXh-r3xSSRRXg@mail.gmail.com>
To: Roberto Peon <grmocg@gmail.com>
Cc: HTTP Working Group <ietf-http-wg@w3.org>, K.Morgan@iaea.org
On May 3, 2014 8:31 AM, "Roberto Peon" <grmocg@gmail.com> wrote:
>
>> - Matthew wrote: "[What about] last-modified? And, possibly, other
fields from Vary? There's more entity-specific metadata than just ETag."
>>
>
> The rule is simple ":uncomressed-foo" replaces "foo" if decompression is
done.
>

Ohh, is this a header pattern? As in, all headers that start with
":uncompressed-" (or whatever) get copied across at the gateway?

So you're effectively sending two complete sets of headers, and optimising
for the overlap.

I can live with this idea, as long as it's made really clear which header
is used by caches and origins for supporting conditionals and ranges in
which situations.

>>
>> - Matthew also wrote: "Cache-Control:no-transform explicitly forbids the
proxy from altering the representation. It's not allowed to decompress it."
>
> I've addressed this. It isn't altering the representation if it is
effectively transmitting both.
>

Yeah, I understand this now; you've theoretically transmitted the
uncompressed entity and all its headers, and the compressed one and all of
its. Two tiers of encoding. And because you can detect support for c-e, you
can choose to only use one or the other, if you want.

It's a pretty conceptually rich change; I'd imagine not a great deal of
code would change, but I think it needs a bit more thinking and discussion
to make sure we end up with something that works properly and doesn't hide
other problems.  Are people happy to invest time into something like this?
Received on Saturday, 3 May 2014 05:57:56 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 17:14:30 UTC