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=41322>.
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=41322


[EMAIL PROTECTED] changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|                            |INVALID




------- Additional Comments From [EMAIL PROTECTED]  2007-01-11 15:53 -------
Ok, this is our fault and not a bug in Tomcat so I'm closing as invalid.

We are using Sitemesh but the page being decorated is in another webapp, so we
have a custom proxy servlet that uses commons-httpclient to fetch the actual
target page. Our code then copies all headers from this proxied response into
the response the user sees. Clearly, not all headers are safe to copy, though:
transfer-encoding in particular!

The nastiest part is that the consequences are intermittent and subtle; as
described the browser occasionally silently ignores a response from the server -
just when the proxied response was returned using chunked encoding, but the
response to the browser is not (because it is the last in a keep-alive
sequence). In this case, the http header indicates chunked, but the
Http11Processor class has (correctly) not configured the ChunkedOutputFilter. 
Ecch.

It would be nice if class Http11Processor would check for the presence of a
Transfer-Encoding header added manually by the user, and either switch to using
the specified encoding or just log an error. However that does have a (small)
performance hit, and very few people are likely to be bitten by this..

-- 
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]

Reply via email to