web-acceleration::max-age functionality

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.