Hello
I need to add <meta http-equiv="Cache-control" content="no-cache"> to about 5 web pages… how should I go about this…
there doesnt seem anywhere in the metadata schema to to meta http-equiv
Kind regards
Angela
Http-equiv - metadata schema
Use cache manager to turn off the cache. The setting should be setting in the response header rather than the html
[quote]
Use cache manager to turn off the cache. The setting should be setting in the response header rather than the html
[/quote]
Thanks, we only want to turn off the cache for certain pages…
[quote]
Thanks, we only want to turn off the cache for certain pages…
[/quote]
The cache manager allows you to configure caching for individual assets, sections of a tree and/or asset types. That includes turning it off or changing the cache expiry time. Take a look here: http://manuals.matrix.squizsuite.net/system-management/chapters/cache-manager#Root-Node-Specific-Screen
Hopefully there is an option that helps you configure caching the way you want.
[quote]
The cache manager allows you to configure caching for individual assets, sections of a tree and/or asset types. That includes turning it off or changing the cache expiry time. Take a look here: http://manuals.matrix.squizsuite.net/system-management/chapters/cache-manager#Root-Node-Specific-Screen
Hopefully there is an option that helps you configure caching the way you want.
[/quote]
Thanks - so if I am understanding it correctly, I just select the root node of the section of the website we dont want to be cached…and change the Caching Status: to be off…while leaving the other as default.
I notice that "Type Code Specific" can override the cache setting for the children assets under the "Root Node Specific". So if you are cascading Root Node Specific, you'd better to set cache for each node.
Maybe it's just a bug in our environment 3.28.8.
[quote]
Thanks - so if I am understanding it correctly, I just select the root node of the section of the website we dont want to be cached…and change the Caching Status: to be off…while leaving the other as default.
[/quote]
The real problem is people are complaining about the pages not being refreshed on their browsers… These people work for another organisation so we do not have any controls over their environment… we need a strategy to ensure no matter what they are getting the current page and do not have to click refresh to receive it.