Good point. I read (again ;-) some sections in RFC 2616 and found:
14.11 Content-Encoding
The Content-Encoding entity-header field is used as a modifier to the media-type. [...] The content-coding is a characteristic of the entity identified by the Request-URI. [...]
*kaboom*. If I understand that correctly, it's *wrong* to serve compressed content under the same URI (and the same *entity*-tag-header). It seems, dynamic compression should be noted in Transfer-Encoding. And... I guess in that case it must not (or should not?) be noted in Vary:.
hmm...???
Nah, ISTR, we have had this discussion before and we said that the ETag should remain the same even when mod_deflate is invovled. The content (barring corruption) should be identical. -- justin
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
