DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=14921>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=14921

reported entity tags differ between HEAD/GET and PROPFIND

[EMAIL PROTECTED] changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[EMAIL PROTECTED]
             Status|NEW                         |RESOLVED
         Resolution|                            |FIXED



------- Additional Comments From [EMAIL PROTECTED]  2003-01-29 17:29 -------
This is not really a bug per se.

What happens is that we generate a weak ETag when the request is too close to 
the modification time of the file (as dictated by RFC 2616, ETags should have 
60-second resolutions).  After that second has elasped and the file hasn't 
changed, that weak entity tag would be made strong.  Creating a weak tag in 
mod_dav_fs isn't always desirable since it isn't keyed to a request - therefore 
all of its entity tags should be strong rather than weak.

However, RFC 2616 explicitly calls out strong entity comparison and weak entity 
comparison functions.  Currently, mod_dav only uses strong entity comparison.  
So, I modified mod_dav to do weak entity comparison instead.

See modules/dav/main/util.c r1.45.

This has been proposed for the next stable release of httpd-2.0.

Thanks for using Apache!

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to