Project

General

Profile

Actions
Copy link

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.

Status:
Closed
Priority:
Normal
Assignee:
Radek Tomiška
Category:
Infrastructure
Target version:
Pyrite (9.5.1)
Start date:
04/04/2019
Due date:
% Done:

100%

Estimated time:
Affected versions:
Owner:

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 issues

Related to IdStory Identity Manager - Task #281: Websocket - new topic for application messagesRejectedRadek Tomiška01/25/2017

Actions
Actions
Copy link
 #1

Updated by Radek Tomiška about 5 years ago

  • Related to Task #281: Websocket - new topic for application messages added
Actions
Copy link
 #2

Updated by Radek Tomiška about 5 years ago

  • 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.

Actions
Copy link
 #3

Updated by Radek Tomiška about 5 years ago

  • 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)
Actions
Copy link
 #4

Updated by Radek Tomiška about 5 years ago

  • 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

I've added version into resource links (js, css), this should help to tell browser about new resource version.

Commit:
https://github.com/bcvsolutions/CzechIdMng/commit/c8e1ddae6ec5d50d9826f2e0b53840af485b469a

Could you try to test it behind some proxy?

Actions
Copy link
 #5

Updated by Ondřej Kopr about 5 years ago

  • 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.

Actions
Copy link
 #6

Updated by Radek Tomiška about 5 years ago

  • Status changed from Resolved to Closed
Actions
Copy link

Also available in: Atom PDF