RE: [squid-users] Sonicwall and empty url

2003-08-19 Thread Alvaro Figueroa
You must use a few configuration parameters on squid.conf that tells
squid it is suppposed to run in 'trasparent' mode.

I am not very familiar myself with squid but I know these options are
fairly well documented inside the squid.conf file.

Regards,
Alvaro Figueroa


-Mensaje original-
De: Vito Parisi [mailto:[EMAIL PROTECTED] 
Enviado el: Martes, 19 de Agosto de 2003 10:14
Para: [EMAIL PROTECTED]
Asunto: [squid-users] Sonicwall and empty url


Hello,
  I am new to Squid and I'd like to use it as a simple cache proxy 
server for web browsing.

We use a Sonicwall appliance for firewalling, and we'd like to use the 
"Proxy Web Server" option of Sonicwall.

This option performs automatic proxy forwarding of all web requests 
coming from the lan (internal) interface of the Sonicwall. Users in the 
lan will use proxy without configuring their browser, because the 
Sonicwall automatically forwards packets to the proxy.

The Squid proxy is currently located on the DMZ, but can be located 
anywhere outside the lan.

Now the problem:

Defining the Squid proxy in the "Proxy Web Server" field of the 
Sonicwall, Squid always returns "Invalid URL", because receives an 
empty URL.

If I use the same proxy from a browser, it works correctly.

Here there is an extract of the Squid Log:

1061296569.027  2 10.192.45.54 NONE/400 1437 GET / - NONE/- 
text/html
1061296572.283  2 10.192.45.54 NONE/400 1437 GET / - NONE/- 
text/html
1061296573.872  1 10.192.45.54 NONE/400 1437 GET / - NONE/- 
text/html
1061296583.608   1245 212.131.168.53 TCP_MISS/200 17744 GET 
http://www.apple.com/ - DIRECT/17.112.152.32 text/html
1061296584.105545 212.131.168.53 TCP_MISS/200 982 GET 
http://statse.webtrendslive.com/S139226/button6.asp? - 
DIRECT/63.88.212.82 image/gif
1061296588.541   4980 212.131.168.53 TCP_MISS/200 1249 GET 
http://statse.webtrendslive.com/S130376/button6.asp? - 
DIRECT/63.88.212.82 image/gif
1061296810.333   1580 212.131.168.53 TCP_MISS/200 92149 GET 
http://www.cisco.com/ - DIRECT/198.133.219.25 text/html

As you can see, the requests from 212.131.168.53 (the browser) are 
performed correctly, while requests from 10.192.45.54 (the redirection 
from the Sonicwall) are empty.

I know (and tried) that the Sonicwall works with other proxies too 
(i.e. Apache), so I don't understand what the problem is.

Any help?

Sincerely,

Vito Parisi




[squid-users] Sonicwall and empty url

2003-08-19 Thread Vito Parisi
Hello,
 I am new to Squid and I'd like to use it as a simple cache proxy 
server for web browsing.

We use a Sonicwall appliance for firewalling, and we'd like to use the 
"Proxy Web Server" option of Sonicwall.

This option performs automatic proxy forwarding of all web requests 
coming from the lan (internal) interface of the Sonicwall. Users in the 
lan will use proxy without configuring their browser, because the 
Sonicwall automatically forwards packets to the proxy.

The Squid proxy is currently located on the DMZ, but can be located 
anywhere outside the lan.

Now the problem:

Defining the Squid proxy in the "Proxy Web Server" field of the 
Sonicwall, Squid always returns "Invalid URL", because receives an 
empty URL.

If I use the same proxy from a browser, it works correctly.

Here there is an extract of the Squid Log:

1061296569.027  2 10.192.45.54 NONE/400 1437 GET / - NONE/- 
text/html
1061296572.283  2 10.192.45.54 NONE/400 1437 GET / - NONE/- 
text/html
1061296573.872  1 10.192.45.54 NONE/400 1437 GET / - NONE/- 
text/html
1061296583.608   1245 212.131.168.53 TCP_MISS/200 17744 GET 
http://www.apple.com/ - DIRECT/17.112.152.32 text/html
1061296584.105545 212.131.168.53 TCP_MISS/200 982 GET 
http://statse.webtrendslive.com/S139226/button6.asp? - 
DIRECT/63.88.212.82 image/gif
1061296588.541   4980 212.131.168.53 TCP_MISS/200 1249 GET 
http://statse.webtrendslive.com/S130376/button6.asp? - 
DIRECT/63.88.212.82 image/gif
1061296810.333   1580 212.131.168.53 TCP_MISS/200 92149 GET 
http://www.cisco.com/ - DIRECT/198.133.219.25 text/html

As you can see, the requests from 212.131.168.53 (the browser) are 
performed correctly, while requests from 10.192.45.54 (the redirection 
from the Sonicwall) are empty.

I know (and tried) that the Sonicwall works with other proxies too 
(i.e. Apache), so I don't understand what the problem is.

Any help?

Sincerely,

Vito Parisi