tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject DO NOT REPLY [Bug 50363] New: Chunked encoding is applied 304 responses with no bodies
Date Mon, 29 Nov 2010 10:42:04 GMT

           Summary: Chunked encoding is applied 304 responses with no
           Product: Tomcat Connectors
           Version: 1.2.30
          Platform: PC
            Status: NEW
          Severity: normal
          Priority: P2
         Component: isapi

When the ISAPI redirector processes a response to a 304 (or 204/205) response
with chunked encoding enabled, and a Content-Length is not specified, chunked
encoding is applied to the empty body, which created an invalid response.

Under normal operation (e.g. DefaultServlet responses), the closing of the
output buffer writes a Content-Length: 0 to the response, which the AJP
connectors don't try to remove for 304 etc. responses (the HTTP connectors do).
This results in 304 responses with Content-Length: 0 headers, which is valid
(if quirky).

This issue can be reproduced by setting a 304 response status and explicitly
calling response.flushBuffer() to commit the response prior to closing the
output buffer.

The ISAPI Redirector also isn't handling a similar case for HEAD requests.

Configure bugmail:
------- You are receiving this mail because: -------
You are the assignee for the bug.

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message