Plugin Support
qtwrk
(@qtwrk)
Hi,
hmmmm , no , can’t set different TTL per post type
but what exactly is it you want to do ?
I don’t understand the relation between 5% pages changes and TTL
once your page is changed, it will purge the cache , you don’t need to bother with TTL
Best regards,
The issue is AMP Cache uses Max Age as the criterion for keeping cache. Even if I purge it on the site, the AMP Cache will follow the Max Age rule. And updating the AMP cache is a bit complicated.
Plugin Support
qtwrk
(@qtwrk)
Hi,
what AMP Cache ?
which max-age you talk about ?
LiteSpeed’s own max-age should not affect anything else than LiteSpeed Cache itself.
Best regards,
It seems to use the max-age of the cache on the site – https://developers.google.com/amp/cache/update-cache
Plugin Support
qtwrk
(@qtwrk)
yeah , but that is cache-control header, which has nothing to do with LiteSpeed Cache
Where do you change that then?
Plugin Support
qtwrk
(@qtwrk)
what is it current value ?
from what I know , all dynamic page from WP has default to cache-control: max-age=0
you can verify your AMP page response header first
you can use htaccess with Header Set directive to change it
Plugin Support
qtwrk
(@qtwrk)
e.g.
Header set Cache-Control "no-cache, no-store, must-revalidate, max-age=0"
apply some SetEnvIf condition , make sure it doesn’t override your static resources’s header
-
This reply was modified 5 years, 2 months ago by
qtwrk.
