httpd-bugs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 14921] - reported entity tags differ between HEAD/GET and PROPFIND
Date Wed, 29 Jan 2003 19:02:02 GMT
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





------- Additional Comments From jerenkrantz@apache.org  2003-01-29 19:02 -------
This is why I believe the only workable solution here is to do weak entity
comparison for the If: header.

mod_dav must be able to handle weak entity tags for its conditional headers
because the entity tag might be promoted from a weak to a strong one at any time
(given rules of 13.3.3).

Note that using ap_make_etag is not an option since we don't have access to the
original request, nor is that resource in the etag hook even related to the
original resource that was requested.  (ap_make_etag has certain configurable
properties that may not be correct if we are not dealing with the original
resource.)  And, doing so, wouldn't solve the real problem of ETag promotion.

If 2518bis clarifies this and says that If should only have strong entity
comparison, then we might want to rethink this.  Regardless, perhaps it should
clarify this corner case.

---------------------------------------------------------------------
To unsubscribe, e-mail: bugs-unsubscribe@httpd.apache.org
For additional commands, e-mail: bugs-help@httpd.apache.org


Mime
View raw message