Thanks, so nothing to worry about. Kind regards Marc -----Ursprüngliche Nachricht----- Von: Amos Jeffries [mailto:squid3@xxxxxxxxxxxxx] Gesendet: Dienstag, 15. Oktober 2013 04:03 An: squid-users@xxxxxxxxxxxxxxx Betreff: Re: Vary object loop On 15/10/2013 1:08 a.m., Grooz, Marc (regio iT) wrote: > Hi, > > what does that message mean in squid 3.3.9? > > varyEvaluateMatch: Oops. Not a Vary object on second attempt, 'http://...' 'accept-encoding="identity,gzip,deflate"' > clientProcessHit: Vary object loop! > > Kind regrads > > Marc Same thing it mens in any Squid version. * The object at the given URL uses Vary header feature of HTTP. - Squid indexes the cache store by URL, so do deal with such features we place a special "vary object marker" in the cache at the index where URL lookup can find it. That object indicates that Vary is used by this resource and what Vary: header key is to be used. Squid then must perform a second cache lookup with the new key to find an object relevant for the current client. The object found by the second lookup is expected to be the real response. * In your case the second lookup discovered a loop back to the same or another vary object. - Squid is just warning you that the cache is corrupted by that loop and will fetch a new object from the network. Amos
<<attachment: smime.p7s>>
