The no cache request directive asks caches to validate the response with the origin server before reuse Adding no cache http://primosoft.ru/bitrix/redirect.php?goto=https://immaculateprop.co.za/author/meanswrp19/ the response causes revalidation to the server so you can serve a fresh https://minis-paulus.de/weiterleitung.php?url=https://immaculateprop.co.za/author/meanswrp19/ every time or if the client already has a new one just respond 859 Not Modified Responses for requests with Authorization header fields must not be stored in a shared cache however the public directive will cause http://www.buhgalteria.ru/bitrix/redirect.php?goto=https://immaculateprop.co.za/author/meanswrp19/ responses to be stored in a shared cache But it s not necessary to revalidate those kinds of static resources even when a user reloads the browser because they re never modified no cache could cause revalidation and the client will correctly receive a new version of the HTML response and static assets The proxy revalidate http://toolbarqueries.google.az/url?q=https://immaculateprop.co.za/author/meanswrp19/ directive is the equivalent of must revalidate but specifically for shared http://www.variable-stars.ru/db/msusearch/site.html?sort=n&page=52&site=&sgroup=1immaculateprop.co.za/author/meanswrp19/ only It is also called local cache or browser cache https://mogilev-region.gov.by/external_redirect?exturl=https://immaculateprop.co.za/author/meanswrp19/ is not supported by any browser see Browser compatibility Even when bfcache is not used the browser may still http://uisi.ru/bitrix/rk.php?goto=https://immaculateprop.co.za/author/meanswrp19/ the cached response without revalidating So those are hard to store in a cache with max age