On 12/8/06, Henrik Nordstrom <[EMAIL PROTECTED]> wrote:
No, that won't work. You still be just as non-conforming by doing that.
But if mod_deflate may to produce different octet-level results on
different requests for the same original entity then it must do this in
addition to other transforms of the ETag.
The identity and gzip encodings is not bidirectionally semantically
equivalent, and additionally normal conditional comparing W/"X" to "X"
is true.
Uh, no, they *are* semantically equivalent - but, yes, not
syntactically (bit-for-bit) equivalent. You inflate the response and
you get exactly what the ETag originally represented.
See RFC 2616 3.3.3 Weak and Strong Validators
You must make the value of the ETag differ between the two entities.
mod_deflate is clearly only doing a semantic (weak) transformation. -- justin
