Hello, I encounter the same problem with my Siebel Web Application. I apply the following instruction in squid.conf : acl MySiebelCL dst 10.0.0.10/255.255.255.255 header_access Accept-Encoding deny MySiebelCL But I don't see any change. The response time are very slow. If I the same access without the proxy/ the response time is better. Do you have any idea ? Thanks for your support, Regards, Mehdi -----Original Message----- From: Henrik Nordstrom [mailto:hno@xxxxxxxxxxxxxxx] Sent: samedi 11 février 2006 15:40 To: Peter Simons Cc: Squid Users Subject: Re: FW: Bypassing Squid for HTTP 1.1 chunked response On Tue, 31 Jan 2006, Peter Simons wrote: > I am trying to resolve a problem when going to a Siebel application via > a Squid Proxy. It seems that the Siebel application (running on IIS > 5.0) is responding to the HTTP 1.0 message with an HTTP 1.1 > "Transfer-encoding: chunked" response as the Siebel application is > finding an "accept-encoding" header in the incoming requests. You can try header_access deny Accept-Encoding this solves identical problem with many other web sites.. This is not a Squid bug. HTTP specifications is very very clear on the point that HTTP/1.1 server MUST NOT respond with chunked encoding in response to HTTP/1.0 requests. > Can anyone help with a way of configuring SQUID to be completely > bypassed for specific transactions i.e. sending the full HTTP 1.1 > request from the client and responding with the full HTTP 1.1 response > for a specified FQDN? This has to be done in the client. Regards Henrik
