Cache Issues: Deployments on our own domain

[JamesCrandall]

I'm hoping to see if others are experiencing problems deploying WAB applications developed with WAB Developer 2.x, specifically, when an existing WAB is re-deployed with updates to the same url address.  Do your user's experience problems with browser caching the original WAB?

In the past we had experienced some problems where user's would navigate to the updated WAB but the updated functionality was not there and the original WAB application was presented.  As a result (at the time) it was decided to publish updated WAB applications to a new url/address and just add a version number to the url.

I'd prefer to simply deploy any updated WAB's to the same url rather than manage new url's with redirects.

Any input is appreciated!

[JamesCrandall]

I'll implement asap!  Much appreciated.

[JamesCrandall]

Robert,

My initial testing shows that your suggested changes to the WidgetManager.js file does in fact resolve the cache issue on the eSearch widget in Chrome Version 61.0.3163.100.  That is very generous to provide the solution and it's greatly appreciated.

I'm not exactly sure how to proceed with this other than running thru a bunch of testing and then presenting those findings and potential solution to the management team here in our organization.  They'll need to decide if modifying an ESRI source component to all of our WAB products is acceptable or not. 

If anything it will likely come back to me for a suggested path forward --- do you see any possibly way that the suggested changes could have negative affects?

Again, your suggestions, solutions and interest in this issue is very much appreciated.

[RobertScheitlin__GISP]

James,

   The only negative affect of this is that the json file will have to be downloaded from the browser each and every time the site is accessed (probably costing a few milliseconds to to most users).