Hit for Pass after "return(pass)" in vcl_recv
Nigel Peck
np.lists at sharphosting.uk
Fri May 12 05:44:24 CEST 2017
Thanks for this. I did some testing and can confirm it won't enter the
cache at all as you say.
Nigel
On 11/05/2017 20:40, Guillaume Quintard wrote:
> IIRC, no it won't because it's a pass, so the new object won't enter the
> cache at all.
>
> --
> Guillaume Quintard
>
> On Thu, May 11, 2017 at 4:40 PM, Nigel Peck <np.lists at sharphosting.uk
> <mailto:np.lists at sharphosting.uk>> wrote:
>
>
> Hi,
>
> I'm wondering what happens with requests that were marked
> return(pass) by vcl_recv, when they get to vcl_backend_response. If
> I do the following:
>
> set beresp.http.Cache-Control = "private, max-age=0, no-cache,
> no-store";
> set beresp.http.Expires = "Mon, 01 Jan 2001 00:00:00 GMT";
> set beresp.ttl = 120s;
> set beresp.uncacheable = true;
> return (deliver);
>
> Is that going to mark them hit-for-pass? Or can they not be cached
> in any way now? (even hit for pass) Is the "uncacheable" redundant
> because they were already marked for pass?
>
> I would appreciate any further info on this.
>
> Thanks
> Nigel
>
> _______________________________________________
> varnish-misc mailing list
> varnish-misc at varnish-cache.org <mailto:varnish-misc at varnish-cache.org>
> https://www.varnish-cache.org/lists/mailman/listinfo/varnish-misc
> <https://www.varnish-cache.org/lists/mailman/listinfo/varnish-misc>
>
>
More information about the varnish-misc
mailing list