Re: store_digest

Allen,

        My guess is that the digest was not yet generated at the time of
the request. You can enable higher debugging levels for digest modules
(see FAQ) and track the time when the digest is created. Note that if
the problem is temporary, Squid will recover automatically by repeating
the request for the digest in a few minutes.

        Also, make sure that the peer name on cache_peer line is the
same as the actual name of the peer. If you use different FQDNs (that
may point to the same cache), internal objects will not work well.
Again, enabling debugging may help you to track down this problem.

Alex.

On Tue, 8 Feb 2000, Allen Wittenauer wrote:

> Any ideas why I would be getting:
>
> 2000/02/08 12:36:14| internalStart: unknown request:
> GET /squid-internal-periodic/store_digest HTTP/1.0
> Accept: application/cache-digest
> Accept: text/html
> Via: 0.0 wcmila:8080 (Squid/2.2.STABLE5)
> X-Forwarded-For: unknown
> Host: wcnwka.iobm.com:8080
> Cache-Control: max-age=259200
> Connection: keep-alive
>
>
> Both wcnwka and wcmila have --enable-cache-digests as a configure option
> when compiled (and, in fact, are using the same binary).
>
>
> Thanks!
>
>
Received on Tue Feb 08 2000 - 19:10:52 MST