The "Fixed" in the bug was applied to TC 5.x. It wasn't until after 4.1.24 was released that I realized that it hadn't been ported to TC 4.1.x. It has since been ported in the CVS (get jakarta-tomcat-connectors with the target coyote_10).
Please don't re-open the bug, since I'll just have to close it again ;-). "Jim Michael" <[EMAIL PROTECTED]> wrote in message news:[EMAIL PROTECTED] > Thanks! Good info, but the interesting thing is that they claim this has > been fixed, when clearly it has not (as of 4.1.24). Does the bug need to > be re-submitted? > > Jim > > >>> [EMAIL PROTECTED] 6/4/2003 9:40:13 PM >>> > This is a known issue. See > http://nagoya.apache.org/bugzilla/show_bug.cgi?id=14292 for more > details. > > "Jim Michael" <[EMAIL PROTECTED]> wrote in message > news:[EMAIL PROTECTED] > > I recently switched from Tomcat 4.0.3 to 4.1.24, and now I'm seeing > > something unexpected: When Tomcat 4.1.24 returns valid content, the > HTTP > > header looks like > > > > HTTP/1.1 200 > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
