Angular works by instantiating code fragments at run time so on load from the browsers viewpoint it is just index.html plus a small mountain of Javascript. Crucially all the modal windows are fragments fn HTML (called partials) that are added and removed as required. This causes some browsers to fail to detect changes - especially in partials.
If this is the case then we need to set cache expires in the REST header to one of:
now
the start time of tomcat
We obviously don't know when RIF40.war needs to be upgraded, so cache-expires should not be set to a future date. The increase in network traffic can be offset by minification.
Angular works by instantiating code fragments at run time so on load from the browsers viewpoint it is just index.html plus a small mountain of Javascript. Crucially all the modal windows are fragments fn HTML (called partials) that are added and removed as required. This causes some browsers to fail to detect changes - especially in partials.
If this is the case then we need to set cache expires in the REST header to one of:
We obviously don't know when RIF40.war needs to be upgraded, so cache-expires should not be set to a future date. The increase in network traffic can be offset by minification.
This can be done in Angular (https://stackoverflow.com/questions/31450738/how-to-define-expiration-time-on-cache-in-angular-cachefactory), but may also need the Tomcat cache-expiry setup.