This is an open question / feature request: I’d like to set 2 expires header lifetimes fot page caching, one default for all the pages, and a second one for a set of custom pages.
Rationale: I have a blog with 5000+ posts dating back since 2003. Posts from the last months are fairly dynamic and receive comments. Archive posts from the past years have closed comments and are failry static.
I’d like to set a default expires header lifetime of, say, 3600 (1 hour) for the last, dynamic posts, and a longer lifetime (a day, a week) for a custom set of pages (say 2003/* 2004/* etc) so that I can benefit from HTML caching.
I get a fair amount of traffic on past years pages from real people and crawlers, but past pages need a longer lifetime in the cache than is optimal for recent posts.
Am I the only one in this situation? Do you think you can include this feature in your roadmap? Do you need further data (web analytics etc)?
- The topic ‘[Plugin: W3 Total Cache] 2 different HTML expires header lifetimes’ is closed to new replies.