Expiration of browser caching for js and css files with wildfly

Question

I have an angularjs javascript application packaged in webapp deployed in Wildfly 8.2.1. Sometimes, when I deploy javascript or css modifications for this webapp, users have to manually delete the browser cache to make changes. Is there a way to change this behavior so that users don’t need to delete their browser cache every time?

Answer 1

I shared this Gist article with you.

It describes how to configure response headers in the wildfly subtype to configure expiration cache headers in the HTTP server response for specific static content such as .js, .css, ... files.