Five New Optimizely Certifications are Here! Validate your expertise and advance your career with our latest certification exams. Click here to find out more
AI OnAI Off
Cache control - max-age goes crazy
I'm experiencing the same problem with max-age, but only on Azure, not on my local IIS.
Did you find a solution Michael?
Nov 11, 2016 17:45
Can you clarify these items:
- R you testing with CDN?
- If it is local what version of IIS r you using?
- Can you share cache section of your web.config?
Aria
Nov 14, 2016 1:43
Turns out it has nothing to do with Episerver. It's a regression in .NET 4.6.2, see https://github.com/Microsoft/dotnet/issues/330
Edited,
Nov 14, 2016 22:25
Kristian You just saved my day, as I was going to investigate it today. Kudos man!
Nov 15, 2016 10:14
This topic was created over six months ago and has been resolved. If you have a similar question, please create a new topic and refer to this one.
Have decorated an Action method with ContentOutputCache attribute, and have set the Duration to 900 sec.
1) First load it`s all fine
Cache-Control:public, max-age=900
2) But after reloading the page, it changes to:
Cache-Control:public, max-age=63613596193
I have no idea, why it changes, for sure it`s not browser related.
Have disabled nearly everything (Episerver plugins, rewrites, adding custom headers) - and still it`s the same.
All I can think of is that is some crazy Episerver issue (v9.12), but it gets even worse, as it behaves the same when I change the ContentOutputCache to OutputCache.
Any tips?