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=42987>. 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=42987 Summary: Weak Etags in Apache are useless and violate RFC 2616, 13.3.3 Product: Apache httpd-2 Version: 2.2.4 Platform: All OS/Version: All Status: NEW Severity: normal Priority: P2 Component: Core AssignedTo: [email protected] ReportedBy: [EMAIL PROTECTED] When Apache cannot create an etag reliably, due to insufficient time resolution, it returns a weak etag. When a client uses this weak etag in a conditional request, it will *never* match. (see test cases) According to RFC 2616, 13.3.3, a weak etag should match, even if the resource has changed, as long as the changes are semantically insignificant. Contrary to this, apache-style weak etags have the meaning "never match". This weak etags are completely useless in any cache validation. No etag would be just as good, except for the missing confusion. For standard HTTP: Apache should send *no* etag or a valid one. For mod_dav: Strong etags are essential for any caching client. As long as the server does not edit the content of resources, it should always send a valid strong etag, even if this affects performance. It should also return a strong etag in a response to PUT. -- 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]
