Output Cache Expiration Date does not match page settings

SOS Childrensvillages asked on February 23, 2018 11:50

Hi, on my root page I have output cache set to Yes and Cache minutes set to 20. All child pages inherit this. However, some cache output items are showing expiry dates of 01/01/2035 or 01/01/2050. I tried clearing the cache, restarting the application pool, disabling and re-enabling the cache.

Is there any other setting that I need to check? I can't see anything in my page types that would be relevant

EDIT: It's a bug in K10 where the output cache = publish until date.

cache output cache

Recent Answers

Peter Mogilnitski answered on February 23, 2018 13:50

The other place is in the System -> Performance -> Output cache. Check the documentaion. Where do see these expiry dates? In debug -> cache itmes?

0 votesVote for this answer Mark as a Correct answer

SOS Childrensvillages answered on February 23, 2018 14:12

Hi Peter, in Settings -> Performance -> Output cache there is only the option to disable or enable output caching (and to set it's dependencies). I see the expiry dates in debug -> cache items like you said

0 votesVote for this answer Mark as a Correct answer

Brenden Kehren answered on February 23, 2018 17:08

Which items are shoting that long expiry date? Kentico doesn't cache all the items, some are IIS dependent but if you're seeing them in the Debug application then it sounds like a Kentico related item. Do you have any configuration in your web.config for caching?

0 votesVote for this answer Mark as a Correct answer

SOS Childrensvillages answered on February 23, 2018 17:38

Hi Brenden, the whole page output is showing the long expiry date. I have nothing extraordinary in my web.config. However, I did add some new keys according to Kentico recommendations.

<add key="CMSUseAutomaticScheduler" value="true" />
<add key="CMSRenewSessionAuthChange" value="true" />

I'll take a look at these on Monday as I don't want to ammend the web.config on a Friday afternoon.

0 votesVote for this answer Mark as a Correct answer

SOS Childrensvillages answered on February 26, 2018 10:12 (last edited on February 26, 2018 10:13)

Nope, wasn't the cache keys either. Here's what I have in web.config that's cache related:

<clientCache cacheControlMode="UseMaxAge" cacheControlMaxAge="7.00:00:00" />

0 votesVote for this answer Mark as a Correct answer

SOS Childrensvillages answered on March 5, 2018 10:14

Should I file a bug then?

0 votesVote for this answer Mark as a Correct answer