- From: Lisa Dusseault <lisa@osafoundation.org>
- Date: Tue, 29 Nov 2005 13:43:15 -0800
- To: Julian Reschke <julian.reschke@gmx.de>
- Cc: WebDAV <w3c-dist-auth@w3.org>
On Nov 29, 2005, at 1:12 PM, Julian Reschke wrote: > > Wilfredo Sánchez Vega wrote: >> Question for you. >> Apache HTTPD emits a weak etag for a file resource if the timestamp >> on the file is the same as the current time (one second accuracy) and >> a strong etag otherwise. >> The reason for that logic, as I understand it, is that because the >> etag generation depends on the timestamp and that the file may change >> multiple times within a one-second period, an etag generated from a >> timestamp matching the current time isn't reliable. > > Finally a good explanation. Do other people consider this behavior to be incorrect according to the spec? (I'm assuming the explanation is correct and it aligns with what I've seen). But it seems that within-second changes do not guarantee "semantic equivalence" as required by HTTP. Lisa
Received on Tuesday, 29 November 2005 21:43:34 UTC