Re: intermediaries, implicit gzip, etags, no-transform

Julian,

did you notice if they correctly set the Vary header to indicate the
content can change depending on Accept-Encoding?

cheers



On 20 June 2014 17:12, Julian Reschke <julian.reschke@gmx.de> wrote:

> Hi there,
>
> so I played around with Google's Data Compression proxy and Opera's Turbo
> today, and found:
>
> - both implicitly use content-coding gzip, but do not touch the Etag,
> potentially breaking HTTP semantics
>
> - GDCP adds a custom header field describing the original content length
> (which of course has not been registered)
>
> - setting "cache-control: no-transform" on the response, does not change
> this behavior, thus both seem to violate a "MUST NOT" requirement from <
> http://greenbytes.de/tech/webdav/rfc7230.html#rfc.section.5.7.2>
>
> Best regards, Julian
>
>
>
>
>


-- 
Greg Wilkins <gregw@intalio.com>
http://eclipse.org/jetty HTTP, SPDY, Websocket server and client that scales
http://www.webtide.com  advice and support for jetty and cometd.