I also have the problem in the past. Use dedicated port for http_port xxx intecept/transparent This resolves the issue. If you use: http_port 3128 http_port 3128 intercept you get your error. But with: http_port 3128 http_port 3129 intercept no error ! -- Best regards, Loïc BLOT, UNIX systems, security and network expert http://www.unix-experience.fr Le mercredi 01 mai 2013 à 10:42 -0300, Pablo Ruben M a écrit : > I have Squid's new installation 3.3.3 behind a Firewall NAT and do not > achieve that it works. Placing the debug in ALL, 3 I obtain the > following mistakes: > > HTTP/1.1 400 Bad Request > Server: squid/3.3.3 > Mime-Version: 1.0 > Date: Wed, 01 May 2013 12:19:08 GMT > Content-Type: text/html > Content-Length: 3229 > X-Squid-Error: ERR_INVALID_URL 0 > Vary: Accept-Language > Content-Language: en > X-Cache: MISS from proxy02 > Via: 1.1 proxy02 (squid/3.3.3) > Connection: close > > In the web browser I obtain: > > The following error was encountered while trying to retrieve the URL: / > > Invalid URL > > I have Squid's installation 2.7 working without problems. Does it > change radically the installation into Squid 3?
Attachment:
signature.asc
Description: This is a digitally signed message part
