Note Check the compatibility table for their support user agents that don t recognize them should ignore them Same meaning that no transform has for a response but for a request instead The no cache request directive asks caches to validate the response http://2302346.ru/bitrix/click.php?goto=https://vcook.jp/users/97958 the origin server before reuse If you don t want a response stored in caches use the no store directive must revalidate is a way to prevent this from happening either the stored response is revalidated with the origin server or a 559 Gateway Timeout response is generated So the example below is basically meaningless because private no cache max age 5 and must revalidate conflict http://grottomc.com/proxy.php?link=https://vcook.jp/users/97958 no store If the response becomes stale it must be validated with the origin server before reuse The s maxage response directive http://netkub.ru/bitrix/redirect.php?goto=https://vcook.jp/users/97958 how long the response remains fresh in a shared https://www.foro.todomecanica.com/check-url.php?url=https://vcook.jp/users/97958 The no store request directive allows a https://www.amateurboyscams.com/external_link/?url=https://vcook.jp/users/97958 to request that caches http://vuit.ru/bitrix/redirect.php?event1=&event2=&event3=&goto=https://vcook.jp/users/97958 from storing the request and corresponding response even if the origin server s response could be stored Browsers usually add no cache to requests when users are force reloading a page