lör 2006-12-09 klockan 19:02 +0100 skrev Justin Erenkrantz: > AIUI, many caches do not allow the response to be cached at all if it > doesn't have an ETag.
Most still caches it, but for example Mozilla has bugs vrt Vary handling if there is no ETag and the conditions changes.. > In the ideal world, I think a weak ETag would be the 'right' thing I don't have an opinion if you return a strong or weak ETag, but it must still be different than the ETag of the identity encoded object, not just the same ETag flagged as weak. Your main decision if the ETag on the mod_deflate generated entity should be weak or strong should be a) If the original entity is weak, then the mod_deflate generated one MUST be weak as well.. b) If mod_deflate can not be trusted to generate the exact same octet representation on each request then the ETag of the generated entity MUST be weak. Else the ETag SHOULD be strong. > however, the current spec doesn't allow conditional GETs to work with > weak ETags. Err.. Weak ETags is allowed in If-None-Match for GET/HEAD. Regards Henrik
signature.asc
Description: Detta är en digitalt signerad meddelandedel
