Summary: | AJP send Body with Status 304 | ||
---|---|---|---|
Product: | Tomcat 7 | Reporter: | Dieter Paradeiser <dieter.paradeiser> |
Component: | Connectors | Assignee: | Tomcat Developers Mailing List <dev> |
Status: | RESOLVED FIXED | ||
Severity: | normal | ||
Priority: | P2 | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Hardware: | PC | ||
OS: | Windows XP |
Description
Dieter Paradeiser
2013-08-20 04:48:03 UTC
So you are saying that AbstractAjpProcessor.prepareResponse needs to have similar logic? Under what conditions is a 304 response being sent along with a body? Is this a Tomcat problem (i.e. a situation where Tomcat itself generates a 304-response with a body) or is this a situation where a webapp can attempt to return a 304 response with a body and you want Tomcat to prevent it from doing so? RFC 2616 does use RFC-MUST-NOT language when referring to 304 responses: "the response MUST NOT contain a message-body". *) same logic, would be solve the problem ;o) **) ajp should also remove the body from response when status 304 is set *) its a webapp, jira from atlassian *) I know about the rfc, I also requested a bug for jira (atlassian-support) Thanks for the report. This has been fixed in 7.0.x and trunk and will be included in 8.0.0-RC2 and 7.0.43 onwards. |