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 > > while Tomcat 4.0.3 returns the normal > > HTTP/1.1 200 OK > > Note that Tomcat is plugged into Apache (I'm not using the catalina > HTTP server!), and content served by Apache directly returns the > expected HTTP/1.1 200 OK header. > > Can anyone tell me *why* Tomcat is doing this? Is such a response even > HTTP compliant? While the site does appear to function normally, the > lack of the "OK" was a surprise (I discovered it when my monitoring > software, which looks for the entire HTTP/1.1 200 OK response, suddenly > said my site was down after upgrading Tomcat <g>) > > Is there a setting in Tomcat 4.1.24 to make the response headers > "normal" again? > > Any info appreciated. > > Jim > > P.S. If you don't follow and want to see what I'm talking about, browse > to http://www.chesterfield.mo.us/site/home.jsp and look at the header! --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
