Description
Problem description:
Currently we use an antiCache GET parameter for our static resources (js, css, img). This parameter is randomly generated at application startup. In a clustered environment each node will therefore have a different antiCache parameter. In addition, it also changes after each application server restart. The effect is that resources are getting reloaded more often than strictly required.
Proposed solution:
Most optimal solution would be to use antiCache parameters that only change if the content of the resource has changed.
Sufficient is to use an application wide hard coded constant antiCache parameter (e.g. a unique constant generated at compile time).