On 12/8/06, Henrik Nordstrom <[EMAIL PROTECTED]> wrote:
The protocol is quite fine as it is, and not easy to change. As it is now it's mainly a matter of understanding that mod_deflate does create a completely new entity from the original one. To the protocol it's exactly the same as when using mod_negotiate and having both the identity and gzip encoded entities on disk. The fact that you do this encoding on the fly is of no concern to HTTP.
mod_deflate is certainly not creating a new resource - it's modifying the representation. There is no legitimate reason for it to modify the ETag other than to mark it as weak. That the caching bits in the RFC didn't understand this speak to the fact that it's quite subtle. -- justin
