Hello,
You may want to upgrade to a 4.1.x or 5.0.x version of Tomcat. I'm having
issues with certain keep-alives in 4.1.27, but other than that the reverse
proxy setup I have seems to work well.
Good Luck!
Brian Peterson
-Original Message-
From: Armenio Pinto [mailto:[EMAIL
dumper output. Tomcat sends a Connection: Close
header, then disconnects, then sends more data.
Any ideas?
Brian Peterson
-Original Message-
From: Brian Peterson [mailto:[EMAIL PROTECTED]
Sent: Tuesday, August 19, 2003 5:46 PM
To: 'Tomcat Users List'
Subject: RE: Tomcat 4.1.18 and SQUID
Many thanks Bill, for a hint.
snip
Tomcat doesn't honor a HTTP/1.0 Connection: keep-alive when it comes from
SQUID. I've upgraded Tomcat to 4.1.27 (latest stable), and I am still
seeing these errors. Any ideas?
Not really. Tomcat is supposed to handle HTTP/1.0 Keep-Alives. You could
try
to the Client App, and then the Client App times out. I
am not doing any special filtering on SQUID.
I've searched Google, Squid FAQ, Squid-users, the Tomcat-users archive.
I'm at a loss, anyone else seen this? Any ideas? Any help appreciated.
Thanks in advance!
Brian Peterson
Let me try again.
I've done a lot of testing, and reading.
Tomcat doesn't honor a HTTP/1.0 Connection: keep-alive when it comes from
SQUID. I've upgraded Tomcat to 4.1.27 (latest stable), and I am still
seeing these errors. Any ideas?
Brian Peterson
-Original Message-
From: Brian