Defect #1596
closed
Force FE cache clean (in browsers) after deploy new version
Added by Marcel Poul about 5 years ago.
Updated about 5 years ago.
Description
When new version of IdM is deployed it is necessary to manually clean cache in user browsers (ctrl+F5). This ticket is intended to find some procedure of proper FE deploy without need of end user interaction.
- Related to Task #281: Websocket - new topic for application messages added
- Status changed from New to In Progress
- Assignee set to Radek Tomiška
- Target version set to Quartz (9.6.0)
Maybe it can be solved old school way - i'll try to add version to 'app.js' resource(s) => 'app.js?version=9-6-0' in build.
- Subject changed from how to force FE cache clean (in browsers) after IdM deploy to Force FE cache clean (in browsers) after deploy new version
- Description updated (diff)
- Category set to Infrastructure
- Target version changed from Quartz (9.6.0) to Pyrite (9.5.1)
- Tracker changed from Task to Defect
- Status changed from In Progress to Needs feedback
- Assignee changed from Radek Tomiška to Ondřej Kopr
- % Done changed from 0 to 90
- Status changed from Needs feedback to Resolved
- Assignee changed from Ondřej Kopr to Radek Tomiška
- % Done changed from 90 to 100
Thank you for fix. We tested with nginx proxy and change app js, this works perfectly thank you.
While we tested same behavior directly by tomcat (connection to port 8080) its works well before. So the issues with cache appears only while we use some proxy (aapche, nginx).
Thanks for fix.
- Status changed from Resolved to Closed
Also available in: Atom
PDF
