Summary: | Missing HTTP header "Content-Type" when response is 304, after a request with "If-Modified-Since" | ||
---|---|---|---|
Product: | Tomcat 5 | Reporter: | Olivier Jaquemet <olivier.jaquemet> |
Component: | Unknown | Assignee: | Tomcat Developers Mailing List <dev> |
Status: | RESOLVED INVALID | ||
Severity: | normal | Keywords: | RFC |
Priority: | P2 | ||
Version: | 5.0.30 | ||
Target Milestone: | --- | ||
Hardware: | All | ||
OS: | All |
Description
Olivier Jaquemet
2006-02-06 16:58:08 UTC
Just for information, as I don't desesperately want this bug to be solved, could you provide the explanation on why this bug won't be fixed? That way I'll try not to submit bug of the same kind in order to limit the amount of bugs you need to deal with. Thanks! :) Proper resolution. The answer is that 304 responses should not contain a Content-Type, according to RFC 2616 section 10.3.5: http://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html#sec10.3.5 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. MSIE does not "go crazy" when receiving a 304 response, so my guess is that the 304 has nothing to do with the observed problems. |