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 39647] - mod_cache sets incorrect Content-type headers for cached context with backend httpd 1.3.33 and mod_jk 1.2.15
Date Sat, 10 Feb 2007 05:36:19 GMT
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=39647>.
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=39647





------- Additional Comments From issues.apache.org@mnot.net  2007-02-09 21:36 -------
10.3.5 says:
 
[[[
If the conditional GET used a strong cache validator (see section 13.3.3), the response SHOULD
NOT 
include other entity-headers. Otherwise (i.e., the conditional GET used a weak validator),
the response 
MUST NOT include other entity-headers; this prevents inconsistencies between cached entity-bodies

and updated headers.
]]]

That applies to the responses; it doesn't specify the behaviour of the cache when it receives
such 
responses.

10.3.5 goes on to say 

[[[
If a cache uses a received 304 response to update a cache entry, the cache MUST update the
entry to 
reflect any new field values given in the response.
]]]

However, your reading does make sense. Rather than try and second-guess an apparent inconsistency

in the spec, I"ll follow up with the HTTP-WG list.


-- 
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: bugs-unsubscribe@httpd.apache.org
For additional commands, e-mail: bugs-help@httpd.apache.org


Mime
View raw message