GreenNet Outreach wrote:
>
> >
> > Your Squid loops back on itself, and therefore denies the request (also
> > quite visibly noted in cache.log).
>
> what! in English??
By some reason Squid thinks the IP address it should contact is it's own
IP.
For an accelerator this can happen in two cases:
a) You are also using the accelerator as a proxy, and try to proxy
requests for the accelerated servers/domains. This is not supported.
Action: configure the no-proxy settings in your browser to not proxy the
accelerated servers/domains (this is only a problem for the people using
the accelerator as a proxy in their browser, not for normal "external"
users)
b) You are running a accelerator with support for multiple
servers/domains and have forgot to map the domain or IP to the real
server. Action: If it is a single server being accelerated, use my
httpd_accel_single_host patch. If it is multiple servers (IP addresses)
being accelerated the setup is a bit trickier. The easiest is to add all
the domains to /etc/hosts, and configure the OS where Squid runs to look
there before DNS. Other options involving redirectors are possible, but
it is not as straight forward.
For a proxy it migth happen if the proxy runs on port 80 and
a) The user tries to browse to the IP address of the proxy, and the
proxy runs on port. Action: Ask the user what they are doing, or ignore
it.
b) Or the server/domainname the user tries to browse to resolves to
127.0.0.1 (or your proxy IP address). Action: Yell at the site owner to
correct their DNS entry, or ignore it.
-- Henrik Nordstrom Squid hackerReceived on Thu Apr 06 2000 - 16:30:51 MDT
This archive was generated by hypermail pre-2.1.9 : Tue Dec 09 2003 - 16:52:51 MST