On 16/05/07, Chris Robertson <crobertson@xxxxxxx> wrote:
Anton Melser wrote: > Hi, > I have searched high and low for this, and can't get anywhere!!! I am > using 2.6.STABLE5 (standard debian etch package). > I am trying to get squid to accelerate both a local apache and a > distant apache (I only want accelerating, nothing else). > If I set squid up on 3128 (with both local and distant apache on 80), > then everything works fine. However, when I set up squid on 80 and > local apache on either 81 (or whatever) or 127.0.0.1:80 then for the > local site I get an access denied. When you change what port Apache is listening on, did you just change the http_port, or did you specify an IP as well in the squid.conf? Did you change the cache_peer line in Squid? Just asking because... > 2007/05/16 19:59:44| WARNING: Forwarding loop detected for: > Client: anip http_port: an_ip.1:80 ...this looks like it could be caused by one (or both) of those. > > Can someone tell me what is going on here? I have tried pretty much > everything I can think of with no luck, and the boss is getting mighty > impatient! > Cheers > Anton Have a peek at the FAQ entries on accelerator setups, if you haven't already. http://wiki.squid-cache.org/SquidFaq/ReverseProxy/ Chris
Thanks Chris, I definitely changed the port (the live sites, which I put in my hosts file so not to cause too much trouble...), and could access with no problems the non localhost sites. I tried both setting a hostname and a ip with the ports - no luck, and had apache2 listening on 127.0.0.7:80 and *.81. I had a very long look at the article mentioned (and you need the right keywords to get to it!) but doing both local and distant reverse proxying wasn't mentioned. I followed the instructions on that page for one of my attempts (with both squid and apache listening on 80 but one localhost and one external) but alas exactly the same results. I have seen in various places about compiling without internal dns but the vast bulk of the literature is on <=2.5, and 2.6 seems pretty different (particularly for http acceleration), and I didn't know whether this was desirable or necessary. Anyway, I will try a couple of things with /etc/hosts, and a few things, but I think it may be due to some resolution issues. Thanks for your input, Anton
