PaulDiNapoli_33
Jan 09, 2019Nimbostratus
web-acceleration::max-age functionality
I'm looking for clarification on the functionality of the web-acceleration profile for the Max Age parameter:
Maximum Age3600 seconds
Does this 3600 second timer only kick in after a cached item is no longer requested? Meaning - as long as it keeps getting hits the timer keeps resetting? I'm working on the assumption that as long as content keeps getting hits the F5 isn't going to age it out for new content. Can't find any documentation beyond the obvious:
"Maximum Age3600 secondsSpecifies the duration in which the system considers the cached content valid"