intermediaries, implicit gzip, etags, no-transform

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

Received on Friday, 20 June 2014 15:12:54 UTC