Forum Discussion

PaulDiNapoli_33's avatar
PaulDiNapoli_33
Icon for Nimbostratus rankNimbostratus
Jan 09, 2019

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"

 

application delivery
BIG-IP

1 Reply

Sort By
  • crodriguez's avatar
    crodriguez
    Ret. Employee
    Jan 09, 2019

    Per our Configuring BIG-IP AAM course, "Content with no expiration indication can be cached by AAM up to a set maximum period before the AAM system goes back to the origin server. This is the Maximum Age setting. Beyond that age, the content is considered stale."

     

    Of course, there are other settings which may impact how or whether Maximum Age is considered. But, as far as how Maximum Age is interpreted, my understanding is that it is not a value that is reset with every touch.