Eliezer Croitoru skrev 2012-11-23 09:13:
On 11/23/2012 10:00 AM, Leslie Jensen wrote:I'm not really sure that I understand the meaning or effect of the above. We do not have browsers configured with proxy. When I set this up a few years back the whole idea was that the users should not have to make any configuration of the browser. Maybe that's why we got the error with 3.2? So if I understand correctly this is what I should do http_port 127.0.0.1:8080 intercept http_port 172.18.0.1:8080 intercept http_port 127.0.0.1:8080 http_port 172.18.0.1:8080The above settings cannot exist! this is since you are using one port paired with IP for intercept. squid must have one http_port XXX what ever if you will use it or not. if you have one port used for either intercept or regular forward proxy you can't use for another whatever use you want so: http_port 172.18.0.1:8080 intercept http_port 127.0.0.1:8080 should be what need. Also I dont know why you should have a 127.0.0.1:8080 with intercept on the same line. I have never seen a use for that in real world unless you are intercepting the local outgoing connections which I doubt is good. But it's your needs. Regards, Eliezer
I've rebuild and installed version 3.2 The message below comes with every site I try to connect to. I understand that a forwarding loop is not good but I fail to see the cause.
2012/11/24 14:10:09 kid1| WARNING: Forwarding loop detected for: GET /Artwork/SN.png HTTP/1.1^M Host: www.squid-cache.org^M User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:6.0.2) Gecko/20100101 Firefox /6.0.2^M Accept: image/png,image/*;q=0.8,*/*;q=0.5^M Accept-Language: sv-se,sv;q=0.8,en-us;q=0.5,en;q=0.3^M Accept-Encoding: gzip, deflate^M Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7^M Referer: http://www.aftonbladet.se/^M Via: 1.1 dentista01.no-ip.org (squid/3.2.3)^M X-Forwarded-For: 172.18.0.100^M Cache-Control: max-age=259200^M Connection: keep-alive^M
Thanks /Leslie
