Re: trouble with cache digests

> On Thu, 8 Jun 2000, Jon Mansey wrote:
>
> > It seems that proxy1 is not serving anything out of its squid-internal space
> >
> > $grep squid-internal access.log
> > 960501394.122 6 <host1> TCP_MISS/400 50 GET
> > http://proxy1.interpacket.net:3128/squid-internal-dynamic/netdb -
> > NONE/- -
> > 960501470.388 1 <host2> TCP_MISS/404 1385 GET
> > http://proxy1.interpacket.net:3128/squid-internal-periodic/store_digest
> > - NONE/- -
> > 960501599.293 1 <host3> TCP_MISS/400 50 GET
> > http://proxy1.interpacket.net:3128/squid-internal-dynamic/netdb -
> > NONE/- -
> > 960501604.685 1 <host4> TCP_MISS/400 50 GET
> > http://proxy1.interpacket.net:3128/squid-internal-dynamic/netdb -
> > NONE/- -
> >
> > It generates a 40x code for any request to squid-internal-*/*

This can happen if "proxy1.interpacket.net" does not realize that it
is named proxy1.interpacket.net. Maybe it has another name?

If you're using a recent version, look for 'hostname_aliases'
in squid.conf.

Duane W.
Received on Thu Jun 08 2000 - 22:30:15 MDT