RE: [squid-users] Using squid 2.4 as an accelerator

I found the problem. When specifying httpd_accel_host you apparently HAVE to
specify the redirect program. I assume this because once I used Brendan's
perl script everything worked smoothly, even though I had explicitly
specified a web server before using:

httpd_accel_host 10.0.0.22

Regards, Dustin

---
Dustin Puryear <dpuryear@usa.net>
Information Systems Consultant
http://members.telocity.com/~dpuryear
In the beginning the Universe was created.
This has been widely regarded as a bad move. - Douglas Adams
> -----Original Message-----
> From: Dustin Puryear [mailto:dpuryear@usa.net]
> Sent: Monday, December 10, 2001 11:22 AM
> To: squid-users@squid-cache.org
> Subject: RE: [squid-users] Using squid 2.4 as an accelerator
>
>
> I am getting what appears to be the infamous "WARNING: Forwarding loop
> detected for" message. I say infamous because the mailing list seems to be
> full of discussions relating to it. However, the answers found in the list
> don't seem to apply to me. I am NOT using cache peering.
>
> Here is a complete error message:
>
> Dec 10 13:11:39 gatekeeper squid[390]: WARNING: Forwarding loop detected
> for: GET / HTTP/1.0^M Accept: text/html, text/plain, text/sgml,
> video/mpeg,
> image/jpeg, image/tiff, image/x-rgb, image/png, image/x-xbitmap,
> image/x-xbm, image/gif, application/postscript, */*;q=0.01^M
> Accept-Encoding: gzip, compress^M Accept-Language: en^M User-Agent:
> Lynx/2.8.4rel.1 libwww-FM/2.14^M Via: 1.0 gatekeeper.actioncore.com:80
> (Squid/2.4.STABLE2)^M X-Forwarded-For: 192.168.0.2^M Host: 192.168.0.2^M
> Cache-Control: max-age=259200^M Connection: keep-alive^M ^M
>
> I am testing Squid internally, and the hostname I am using is in
> /etc/hosts,
> but is fake for now. Its IP address is 192.168.0.2, and is dual homed with
> the webservers in 10.0.0.0/24 behind it. I have tried accessing
> the page via
> lynx both on the local Squid machine and remotely and get:
>
> [--snip--]
>    While trying to retrieve the URL: http://192.168.0.2/
>
>    The following error was encountered:
>      * Access Denied.
>        Access control configuration prevents your request from
> being allowed
> at this time. Please contact your service provider
>        if you feel this is incorrect.
>
>    Your cache administrator is webmaster.
>
>    Generated Mon, 10 Dec 2001 19:11:39 GMT by gatekeeper.actioncore.com
> (Squid/2.4.STABLE2)
> [--snip--]
>
> My configuration is pretty simple:
>
> [---snip---]
> http_port       0.0.0.0:80
> visible_hostname        gatekeeper.actioncore.com
> cache_effective_user    squid
> cache_effective_group   squid
> acl     all             src     0.0.0.0/0.0.0.0
> http_access     allow   all
> httpd_accel_host        10.0.0.22
> httpd_accel_port        80
> httpd_accel_uses_host_header    on
> [---snip---]
>
> I purposely have Squid wide open with 'http_access allow all' for testing
> purposes. Note that gatekeeper is a FreeBSD router between networks
> 192.168.0.0/24 and 10.0.0.0/24. The webservers are in 10.0.0.0/24.
>
> Any clues what the problem could be?
>
> Regards, Dustin
>
> ---
> Dustin Puryear <dpuryear@usa.net>
> Information Systems Consultant
> http://members.telocity.com/~dpuryear
> In the beginning the Universe was created.
> This has been widely regarded as a bad move. - Douglas Adams
>
>