<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman",serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri",sans-serif;
mso-fareast-language:EN-US;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:70.85pt 70.85pt 70.85pt 70.85pt;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang="FR-CA" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal"><span lang="EN-CA" style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D;mso-fareast-language:EN-US">So in which case would you want to force it to false? I read about it and it's mainly used to force a hit for pass, but
I haven't read about a scenario where the opposite would be useful.</span><span lang="EN-CA" style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"><o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-CA" style="mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><b><span lang="FR" style="font-size:11.0pt;font-family:"Calibri",sans-serif">De :</span></b><span lang="FR" style="font-size:11.0pt;font-family:"Calibri",sans-serif"> Guillaume Quintard [mailto:guillaume@varnish-software.com]
<br>
<b>Envoyé :</b> vendredi 21 juillet 2017 03:49<br>
<b>À :</b> Girouard, Yanick <Yanick.Girouard@stm.info><br>
<b>Cc :</b> Andrei <lagged@gmail.com>; varnish-misc@varnish-cache.org<br>
<b>Objet :</b> Re: Varnish and max-age=0<o:p></o:p></span></p>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p class="MsoNormal">Common mistake, beresp.uncacheable isn't the opposite of beresp.ttl>0. "uncacheable" tells Varnish that if it gets a HIT for that object, it should convert it to a PASS/MISS (depending on the versions) and avoir request coalescing. In that
scenario too, the ttl is the time the object will live in cache. ie. how long do you retain the memory that it's not cacheable.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><br clear="all">
<o:p></o:p></p>
<div>
<div>
<div>
<div>
<p class="MsoNormal">-- <o:p></o:p></p>
</div>
<p class="MsoNormal">Guillaume Quintard<o:p></o:p></p>
</div>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p class="MsoNormal">On Fri, Jul 21, 2017 at 12:09 AM, Girouard, Yanick <<a href="mailto:Yanick.Girouard@stm.info" target="_blank">Yanick.Girouard@stm.info</a>> wrote:<o:p></o:p></p>
<blockquote style="border:none;border-left:solid #CCCCCC 1.0pt;padding:0cm 0cm 0cm 6.0pt;margin-left:4.8pt;margin-right:0cm">
<p class="MsoNormal">That's a good thought, but what would really be the impact of this setting if I've already set the ttl to a positive value after stripping all headers that would make Varnish consider the object as being uncacheable to begin with? Is there
a case where it would be required?<br>
<br>
<br>
________________________________<br>
De : Andrei <<a href="mailto:lagged@gmail.com">lagged@gmail.com</a>><br>
Envoyé : 20 juillet 2017 15:22<br>
À : Girouard, Yanick<br>
Cc : Reza Naghibi; <a href="mailto:varnish-misc@varnish-cache.org">varnish-misc@varnish-cache.org</a><br>
Objet : Re: Varnish and max-age=0<br>
<br>
Just a thought, if you're going to force an otherwise uncacheable request to be cached, you should probably: set beresp.uncacheable = false;<br>
<br>
<br>
<br>
On Thu, Jul 20, 2017 at 9:03 PM, Girouard, Yanick <<a href="mailto:Yanick.Girouard@stm.info">Yanick.Girouard@stm.info</a><mailto:<a href="mailto:Yanick.Girouard@stm.info">Yanick.Girouard@stm.info</a>>> wrote:<br>
Hi Reza,<br>
<br>
Yes we are. Here's the default we apply. Those two subs are called in order in vcl_backend_response:<br>
<br>
/* REMOVE CACHE-CONTROL AND SURROGATE-CONTROL FROM BACKEND *<br>
***********************************************************/<br>
sub stm_backend_resp_unset_cache_control_headers {<br>
unset beresp.http.Surrogate-Control;<br>
unset beresp.http.Cache-Control;<br>
unset beresp.http.Expires;<br>
}<br>
<br>
/* DEFAULT ALL TO: TTL 30MIN + GRACE 15MIN *<br>
*******************************************/<br>
sub stm_backend_resp_expiration_default {<br>
set beresp.ttl = 30m;<br>
set beresp.grace = 15m;<br>
}<br>
<br>
That doesn't seem to have any impact when the backend responds with a Cache-Control: max-age=0 header.<br>
<br>
Any idea?<br>
<br>
<br>
De : Reza Naghibi [mailto:<a href="mailto:reza@varnish-software.com">reza@varnish-software.com</a><mailto:<a href="mailto:reza@varnish-software.com">reza@varnish-software.com</a>>]<br>
Envoyé : jeudi 20 juillet 2017 13:58<br>
À : Girouard, Yanick <<a href="mailto:Yanick.Girouard@stm.info">Yanick.Girouard@stm.info</a><mailto:<a href="mailto:Yanick.Girouard@stm.info">Yanick.Girouard@stm.info</a>>><br>
Cc : <a href="mailto:varnish-misc@varnish-cache.org">varnish-misc@varnish-cache.org</a><mailto:<a href="mailto:varnish-misc@varnish-cache.org">varnish-misc@varnish-cache.org</a>><br>
Objet : Re: Varnish and max-age=0<br>
<br>
The TTL is calculated before entering vcl_backend_response. So eventhough you unset the Cache-Control header, the value of TTL will be calculated based on it. Are you setting a new value for beresp.ttl? You need to do that:<br>
<br>
sub vcl_backend_response<br>
{<br>
unset beresp.http.Cache-Control;<br>
set beresp.ttl = 120s;<br>
}<br>
<br>
--<br>
Reza Naghibi<br>
Varnish Software<br>
<br>
On Thu, Jul 20, 2017 at 1:44 PM, Girouard, Yanick <<a href="mailto:Yanick.Girouard@stm.info">Yanick.Girouard@stm.info</a><mailto:<a href="mailto:Yanick.Girouard@stm.info">Yanick.Girouard@stm.info</a>>> wrote:<br>
Hi,<br>
<br>
We use Varnish to cache for multiple backends and need Varnish to always control what is cached despite what backends could respond. In other words, even if a backend sets Cache-Control headers to never cache its pages, we still want Varnish to cache them based
on defined rules (i.e. certain URL patterns or hosts have different TTLs).<br>
<br>
We have recently realized that one of our backend always set the following header: Cache-Control: max-age=0, private, must-revalidate<br>
<br>
Our VCL unsets the Cache-Control header in vcl_backend_response and sets its own before delivering. By unsetting the Cache-Control header in vcl_backend_response I would expect Varnish to ignore the max-age=0 value and still cache the page as per our other
rules, but it seems that the second it sees max-age=0 in the response header, that it makrs the object as not cacheable.<br>
<br>
Other than by changing the backend's response to never set max-age=0, is there a way to force Varnish to cach pages even if it returned max-age=0?<br>
<br>
Is this even by design or is it a bug?<br>
<br>
Thanks,<br>
Yanick Girouard<br>
<br>
<br>
_______________________________________________<br>
varnish-misc mailing list<br>
<a href="mailto:varnish-misc@varnish-cache.org">varnish-misc@varnish-cache.org</a><mailto:<a href="mailto:varnish-misc@varnish-cache.org">varnish-misc@varnish-cache.org</a>><br>
<a href="https://www.varnish-cache.org/lists/mailman/listinfo/varnish-misc" target="_blank">https://www.varnish-cache.org/lists/mailman/listinfo/varnish-misc</a><br>
<br>
<br>
_______________________________________________<br>
varnish-misc mailing list<br>
<a href="mailto:varnish-misc@varnish-cache.org">varnish-misc@varnish-cache.org</a><mailto:<a href="mailto:varnish-misc@varnish-cache.org">varnish-misc@varnish-cache.org</a>><o:p></o:p></p>
<div>
<div>
<p class="MsoNormal"><a href="https://www.varnish-cache.org/lists/mailman/listinfo/varnish-misc" target="_blank">https://www.varnish-cache.org/lists/mailman/listinfo/varnish-misc</a><br>
<br>
<br>
_______________________________________________<br>
varnish-misc mailing list<br>
<a href="mailto:varnish-misc@varnish-cache.org">varnish-misc@varnish-cache.org</a><br>
<a href="https://www.varnish-cache.org/lists/mailman/listinfo/varnish-misc" target="_blank">https://www.varnish-cache.org/lists/mailman/listinfo/varnish-misc</a><o:p></o:p></p>
</div>
</div>
</blockquote>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</div>
</body>
</html>