Thursday, March 22, 2012 11:19 AM
The issue does not get resolved after closing all the browser instance or restarting the server. The only way to fix is to delete/clear the temporary internet files or force the browser to ‘Always refresh from server’.
OS: Windows 7 with SP1
Browser: IE 9 - Version: 9.0.8112.16421
Current Code block:
Workaround over Internet
But, we cannot add everytime unqiue numbers to all changed JS files as we have to release .ASPX pages also every time even code changes are there in JS files.
Same problem is happening with Image files also and its practiclly not possible to add unique number to all changed images because of some are in CSS files and some are in ASPX pages.
Is there any better way to address this problem without much code changes in every release?
- Edited by sekhar babu madala Thursday, March 22, 2012 11:20 AM
Monday, March 26, 2012 3:30 AM
It appears IE won't send request to server when user simply puts focus back in the address bar and hits Enter. I used to inform customers refresh the page by clicking the refresh button, hitting F5 or using a super refresh(holds Ctrl while refreshing).
Tuesday, March 27, 2012 4:31 PM
Sekhar, I have same problem. I've been having issues with website not refreshing content. I recently changed from using IE9 as my default web browser for testing, instead of IE8. I’ve noticed that IE9 seems very temperamental with regards reloading the files and seems to stick with the cached copy. This obviously results in latest changes not being displayed when customer look at the site live.
It is not feasible for customers to ask for IE setting to be "check every time I visit this page option". The first question they are going to ask WHY, and I cannot give IE9 as a reason.
Here are few links on internet and I see others out there are having same/similar problems, but no one has suggested proper solution.
Microsoft... Please help
Franconia - The problem is not with the browser - addressbar. Your suggestion does not apply here.
Saturday, August 04, 2012 11:26 AM
This is not Microsoft issue. Our solution is to add cache expiration header for js/css/image files (e.g. 24 hours). This way, when you deliver a new release to the customer, the customer can at least get the latest version of js/css/image files after 24 hours.
Another solution that we consider is to change the context path for each new release and append the version number at the end (e.g. /appName/V2). As it is impossible to tell the customer to switch the url for each new release, we'll do a redirect at server side (e.g. redirect /app to /appName/v2). This way, it looks transparent to the cusotmer.
Saturday, August 04, 2012 11:29 AMActually recently we encounter a very wierd issue, it only happened at very few machine occaisally. After the cache expiration, IE still reads from cache. Even after we tell the user to delete the temp file, the cilent browser is still using the old version (don't understand where the cache is). It can only be solved to force to the browser to "always refresh from the server". Is there anyone who encounter simillar issues? Any thought?