sön 2006-10-22 klockan 08:28 -0700 skrev Reza: > If I tail the dansguardian.log on 192.168.0.12 I see the following. > > article/2006/10/21/AR2006102100487.html GET 1289 > 2006.10.21 22:32:09 - 192.168.1.37 > http://www.washingtonpost.com/wp-dyn/content/ > > At the same time I get the following in the squid access log. > 1161470040.990 7 192.168.0.12 TCP_DENIED/400 1659 GET > /wp-dyn/content/article/2006/10/21/AR2006102100487.html - NONE/- text/html Looks like DG is forwarding the request to Squid as a web server request, not a proxy request. > Now an interesting thing to note is that if I open Internet Explorer and go > to Tools -> Internet Options -> Connections -> Lan Settings -> and set the > proxy server to 192.168.0.12:8080 while mainting the already set NAT > Redirection rule the proxy will work just fine. Ah, you are using DG for transparent interception? Does DG support this? If not you will see better results by configuring NAT -> Squid 1 -> DG -> Squid 2 where Squid 1 and Squid 2 is two different instances of Squid, where the job of the first is to properly accept the transparently intercepted request before it's sent to DG. Regards Henrik
Attachment:
signature.asc
Description: Detta =?ISO-8859-1?Q?=E4r?= en digitalt signerad meddelandedel
