I don't understand why this was marked as the accepted solution. I appreciate the response but it did not address my actual question.

Yes, I'm aware of the alternatives. I would still like to see if anyone can answer my original question about the feature that exists OOTB in AEM.

Yeah, I can set expires headers using the path and file type. That's not a problem. My scenario is for clientlibs with CSS/JS that constantly change. So if new changes get pushed, how does it get invalidated? The point of the version string is that the browser/CDN knows that the file has changed and...

Yes, I get that, but in order to have far-future expires headers in Apache or the CDN I need to have a version string or hash of some sort on the clientlib include.

There is a "long cache" feature in the com.adobe.granite.ui.clientlibs.impl.HtmlLibraryManagerImpl which apparently has similar functionality to ACS Commons Versioned Clientlibs. However, I can't find any documentation on how it's supposed to work. I've tried this out locally and when I set the "htm...