RE: http_accel and forwarding loops

Yes, this is the same problem I reported two days ago with 2.1RELEASE.
You will find that if you change the httpd_accel_port to a false port, you
will no longer get the loop error, you will get a "cannot contact"
or something like that.

This means that squid looks at http_accel_port, but NOT at httpd_accel_host,
at least in our circumstances.

john harris

-----Original Message-----
From: Jens-Uwe Mager
To: uunet!ircache.net!squid-users
Sent: 1/9/99 5:49 PM
Subject: http_accel and forwarding loops

I just did the upgrade to squid-2.1.PATCH2 from squid 1.x and I have a
strange problem with a forwarding loop. I do run Squid as cache as well
as http accelerator as the main webserver is behind a slow leased line.
This is all fine and well with one exception: if local users do not
explicetely configure to not cache the www server, they will get an
access denied error due to a forwarding loop. The configuration is as
follows:

proxy server is shadow.han.de on port 80, www.han.de is a cname for
shadow.han.de. http_accell_host is harlie.han.de. Always_direct is set
to allow for both www.han.de and harlie.han.de.

If a proxy request for www.han.de comes in, squid now contacts itself
instead of harlie.han.de directly and the error occurs. Is there any way
to configure squid to redirect the proxy request to harlie.han.de
directly?

--
Jens-Uwe Mager <pgp-mailto:62CFDB25>