Hello,

> Incoming connection from /127.0.0.1
> New connection thread
> localhost:8090
> TARGET=/tomcat-docs/jndi-datasource-examples-howto.html
>>> Request URI: /tomcat-docs/jndi-datasource-examples-howto.html
> << Response: HTTP/1.1 200 OK
> Connection kept alive...
> CONTENT LENGTH: 51619 ||CONTENT WRITE 7984

Have you checked the actual size of that file in
the file system? Maybe tomcat is reporting a wrong
content length for some reason. If the end of the
message body is indicated by closing the connection,
that might go without an exception anywhere.
It might also be worth to have a look at other
Content headers, like Content-Encoding. Content
compression could be an explanation, in particular
if your proxy is forwarding headers from the client
indiscriminately (which it shouldn't).

cheers,
  Roland


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to