2009/11/16, Amos Jeffries <squid3@xxxxxxxxxxxxx>: > Werner Müller wrote: >> Hello, >> >> i have SQUID 2.7 STABLE 6 running under windows. >> Squid runs on a dedicated machine and on a other Server (for example, >> ip: 1.1.1.1) a Internet Traffic Virus Scan application on port 3128 is >> installed. On the Internet Traffic Virus Scan application is >> configured a other upstream proxy on port 8080. >> >> Here the cache_peer line from my squid.conf: >> >> cache_peer 1.1.1.1 parent 3128 0 default no-query no-digest >> >> When i access to a website it opens >> http://auto.search.msn.com/response.asp?... >> >> If i configure the hosts file to "localhost 1.1.1.1" and change the >> cache_peer entry to: >> cache_peer localhost parent 3128 0 default no-query no-digest >> >> the website is able to access. > > So ... whats the problem? > > Also, "localhost" is a dedicated network name which should never be > anything other than 127.0.0.1 the secure "local host loopback". > Please do not point it at public IPs, that will screw your security over > quite badly. > > Amos > -- > Please be using > Current Stable Squid 2.7.STABLE7 or 3.0.STABLE20 > Current Beta Squid 3.1.0.14 > The Problem is, that i cannot reach a Server over the IP: with this cache_peer entry i get a failure: cache_peer 1.1.1.1 parent 3128 0 default no-query no-digest The localhost entry was only a test. But it's very strange that it works with the localhost entry (localhost 1.1.1.1) and if i change the cache_peer entry in squid.conf it will not work. Here the entries from cache.log: ... | TCP connection to 1.1.1.1 (1.1.1.1:3128) failed Detected DEAD Parent: 1.1.1.1 | TCP connection to 1.1.1.1 (1.1.1.1.1:3128) failed | temporary disabling (Gateway Time-out) digest from 1.1.1.1 TCP connection to 1.1.1.1 (7.21.32.137:3128) failed ... (I changed the real IP for this post to 1.1.1.1)
