Re: trouble with cache digests

Jon,

        The first thing to check is that Proxy1 is known to Proxy2
under the same name Proxy1 is known to itself. For example, if Proxy1
thinks it's name is "proxy1.interpacket.net" while Proxy2 talks to
"one.proxies.interpacket.net", digests may not work.

        Also, make sure that Proxy1 is generating a digest (see FAQ).
The fact that a proxy is using others digests does not mean it has
its own digest.

        Finally, wait and see if the problem goes away after, say 20
minutes. There are moments when digest is not available to peers; peers
will retry later.

Alex.

On Wed, 7 Jun 2000, Jon Mansey wrote:

> I have strange problem enabling cache digests on one of my boxen.
>
> I have digests working fine on proxy2, it serves its digests to
> others and uses others digests just fine.
>
> Proxy1 is using its siblings' digests just fine but when I try to
> pull proxy1's digest to proxy2, proxy1 complains with this error in
> cache.log
>
>
> 2000/06/07 17:54:30| internalStart: unknown request:
> GET /squid-internal-periodic/store_digest HTTP/1.0
> Accept: application/cache-digest
> Accept: text/html
> Via: 0.0 <proxy2>:3128 (Squid/2.2.STABLE5)
> X-Forwarded-For: unknown
> Host: <proxy1>:3128
> Cache-Control: max-age=259200
> Connection: keep-alive
>
> and proxy2's cache.log reports
>
> 2000/06/07 17:59:32| temporary disabling (Not Found) digest from <proxy1>
>
> Any ideas what could be afoot here folks? Its 2.2S5 BTW.
>
> TIA,
>
> Jon.
>
>
>
>
>
Received on Thu Jun 08 2000 - 09:01:26 MDT