Thanks Eric and Prasanna.
To answer - all .htm pages are served by tomcat, so apache acts only as a proxy.
Some .htm pages work, others don't.
When I try the HTTP connector from Tomcat, these pages that don't work
return an incomplete status line: "HTTP/1.x 200" , instead of
"HTTP/1.x 200 OK" (t
You mentioned some html pages only have this wierd problem. Are all those
problematic htmls are in tomcat or only some of them in tomcat and rest
in Apachel?
Regards
Prasanna Ram
On Wed, Apr 8, 2009 at 3:32 PM, Marius Hanganu wrote:
> Thanks for responding.
>
> I am indeed using mod_proxy, but
Thanks for responding.
I am indeed using mod_proxy, but no special configuration. Only
ProxyPass settings.
Thanks,
Marius
On Wed, Apr 8, 2009 at 8:33 AM, Prasanna Ram Venkatachalam
wrote:
> Its really wierd!
> I think 'Apache-Coyote' is the server header from Tomcat and if the header
> is from
Its really wierd!
I think 'Apache-Coyote' is the server header from Tomcat and if the header
is from Apache, it shud be 'Apache'. Since u say that tomcat serve the pages
correctly. I guess u are using mod_proxy to redirect the page to tomcat. Am
i right? If thats the case theres is something in mod
Hello,
I'm facing this weird issue on a gentoo machine with apache 2.2 +
mod_proxy + tomcat.
Some .htm pages (not all) contain - right on top of the page - a dump
of the HTTP headers. Something like:
HTTP/1.1 0 Server: Apache-Coyote/1.1 Set-Cookie: JSESSIONID=
This is not because of Tomcat,
