Hi Alex,
Thanks for the information. Could you elaborate on when collapsed forwarding does apply? With your extra information, my assumption would be that it only applies on requests of a resource that has never been cached before. Or does it make more sense in a distributed Squid setup? Not sure if I'm missing something.
Secondly would you have a suggestion for solving the issue I'm facing?
Best regards
2016-06-15 17:19 GMT+02:00 Alex Rousskov <rousskov@xxxxxxxxxxxxxxxxxxxxxxx>:
On 06/14/2016 02:51 AM, Jaap Dam wrote:
> I've part of the logging as an attachment. I'm requesting a single URL
> in this log. The log starts with a stale cache of the item.
Collapsed forwarding does not apply to cache revalidation requests yet.
Factory is working on implementing collapsed revalidations (in some
environments), but I cannot promise a specific delivery date or that
your particular environment will be covered.
Alex.
> 2016-06-13 15:34 GMT+02:00 Amos Jeffries:
>
> On 14/06/2016 12:29 a.m., Jaap Dam wrote:
> > Is the collapsed_forwarding directive the correct one to use for my
> > use-case or am i missing something?
>
> Yes it is correct so far as I am understanding your need.
>
> For further debugging about what is going on you will need the HTTP
> messages involved. Add the directive "debug_options 11,2 20,3" to your
> config to get them logged in cache.log.
_______________________________________________ squid-users mailing list squid-users@xxxxxxxxxxxxxxxxxxxxx http://lists.squid-cache.org/listinfo/squid-users
