I believe my homepage is being cached. I get the same timestamp upon reload for awhile...But, I end up getting newer timestamps after awhile, when even no posts have been updated.
I believe this is because I have the defaults selected for Purge Policy on the Page Caching tab:
Specify the pages and feeds to purge when posts are created, edited, or comments posted. The defaults are recommended because additional options may reduce server performance: Home page Post page Blog feed
Our site gets a ton of spam comments, so I'm thinking that when a comment is posted, our homepage is getting purged causing it to be regenerated again.
Can anyone confirm this is how W3TC is working?
We do not approve any comments automatically, so I would really like this policy to be based on when a comment is approved, instead of just posted...This would cut down when the homepage is auto generated, if this is the case.
Another solution, would be to have a way to separate the purge policy for Homepage from comments somehow. My first thought was to deselect Homepage in the Purge Policy section, but when I read the section, and interpret it, this means, that when a post is created or edited, then the homepage would not be purged, which is NOT what I want to happen. I just want the Homepage to not be purged when new comments are made.
I believe people brought this up in this thread:
But the developer never quite understood the benefit of doing this.
Does my explanation make sense?