<div dir="ltr">IIRC, no it won't because it's a pass, so the new object won't enter the cache at all.</div><div class="gmail_extra"><br clear="all"><div><div class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr"><div>-- <br></div>Guillaume Quintard<br></div></div></div>
<br><div class="gmail_quote">On Thu, May 11, 2017 at 4:40 PM, Nigel Peck <span dir="ltr"><<a href="mailto:np.lists@sharphosting.uk" target="_blank">np.lists@sharphosting.uk</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><br>
Hi,<br>
<br>
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:<br>
<br>
set beresp.http.Cache-Control = "private, max-age=0, no-cache, no-store";<br>
set beresp.http.Expires = "Mon, 01 Jan 2001 00:00:00 GMT";<br>
set beresp.ttl = 120s;<br>
set beresp.uncacheable = true;<br>
return (deliver);<br>
<br>
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?<br>
<br>
I would appreciate any further info on this.<br>
<br>
Thanks<br>
Nigel<br>
<br>
______________________________<wbr>_________________<br>
varnish-misc mailing list<br>
<a href="mailto:varnish-misc@varnish-cache.org" target="_blank">varnish-misc@varnish-cache.org</a><br>
<a href="https://www.varnish-cache.org/lists/mailman/listinfo/varnish-misc" rel="noreferrer" target="_blank">https://www.varnish-cache.org/<wbr>lists/mailman/listinfo/varnish<wbr>-misc</a><br>
</blockquote></div><br></div>