Details
-
Bug
-
Status: Resolved
-
Major
-
Resolution: Fixed
-
1.2.13-core , 1.2.14-core , 2.0.0-beta-1
-
None
-
None
-
All
Description
The Agent Version support uses the hash code of enums as part of its hash code. Since the enum hash code is based on the memory address of the enum, this causes the hash code on the cached css file to change every time the server is restarted even if the css file itself did not change. The result is the user agent pull new copies of the CSS file more often than necessary.
The solution is to use the hash code of the enum's name instead, which is stable.
Doing so I now see the same hash code ( "d8dxpq" in the case of the rich client fusion skin on JSF2) across runs rather than different values("iyn8lw" and "idkr6t") like I did before