"Brian Peterson" <[EMAIL PROTECTED]> wrote in message news:[EMAIL PROTECTED] > 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? >
Not really. Tomcat is supposed to handle HTTP/1.0 Keep-Alives. You could try enabling the RequestDumper and posting the results. It looks like the 100-continue is being generated by SQUID (since Tomcat would reply with "HTTP/1.1 100 Continue", if it saw a "Expect: 100-continue" header). > Brian Peterson > > -----Original Message----- > From: Brian Peterson [mailto:[EMAIL PROTECTED] > Sent: Monday, August 11, 2003 1:39 PM > To: [EMAIL PROTECTED] > Subject: Tomcat 4.1.18 and SQUID > > > Tomcat Experts, > > I have the following setup. > > (1) Client App --> SQUID --> Tomcat 4.1.18 > and > (2) Client App --> Tomcat 4.1.18 > > Where Client App is a program, not a webuser. When I remove SQUID, the > Client App seems to function normally. With SQUID, I get an HTTP/1.0 100 > Continue going back 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 > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
