DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUGĀ· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://issues.apache.org/bugzilla/show_bug.cgi?id=38034>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED ANDĀ· INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=38034 ------- Additional Comments From [EMAIL PROTECTED] 2008-01-04 22:53 ------- Just a question related to this issue - not sure if I'm 100% correct in my thinking yet... Did ap_meet_condition fail because the ETag for the non-existant file is constantly changing (mtime only ETag from http_etag.c) as there is no finfo (as a by product of it not existing)? locks on non-existent files create a .DAV/.locknull so a resource does actually exist (a lock-null resource)? is this correct? I'm happy with the present work-around but if what i'm thinking is the case then a cleaner fix in the future could be having mod_dav always providing its ETags (overriding http_etag for DAV directories) and as it knows about lock-null resources it could use the .locknull file for a constant inode-size-mtime Etag instead of just mtime, making ap_meets_condition happy? That's if my assumptions are correct. -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
