You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@tomcat.apache.org by bu...@apache.org on 2008/04/09 00:04:20 UTC

DO NOT REPLY [Bug 44448] Invalid Response if HTTP Status = 304

https://issues.apache.org/bugzilla/show_bug.cgi?id=44448


Mark Thomas <ma...@apache.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|REOPENED                    |RESOLVED
         Resolution|                            |WORKSFORME




--- Comment #4 from Mark Thomas <ma...@apache.org>  2008-04-08 15:04:20 PST ---
I have just checked this with:
httpd 2.2.4
mod_proxy_ajp
Tomcat 5.5.HEAD

I have stepped through the code and Tomcat correctly sets a content length of
zero. Further, an examination of the headers received by the UA do not show any
invalid content length.

I don't see how this could be happening as to get the behaviour described here
you would have to have replaced Tomcat's DefaultServlet.

I am resolving this as worksforme for now but I am more than happy to look at
this further if you can provide the steps to reproduce from a clean install of
all components (mod_proxy_ajp preferred). You should be able to reproduce the
error using tomcat.gif file in the ROOT webapp.


-- 
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org