Last post Nov 13, 2013 03:08 AM by Steven Cheng - MSFT
Nov 11, 2013 11:06 AM|airic82|LINK
An issue we've found during development is that when we make amendments to the JS file, the server continues to load a cached version, which means it's not picking up the changes we made and usually causes things to break.
On the WebMethod, we've set the cache to 30 minutes, but even commenting that out temporarily doesn't fix this issue, nor does clearing the browser's cache.
Does anyone have any ideas on how we can work around this?
Nov 12, 2013 08:15 AM|Illeris|LINK
Nov 13, 2013 03:08 AM|Steven Cheng - MSFT|LINK
For the caching you mentioned, are you using the standard HTTP cache or ASP.NET caching function? For standard HTTP caching, we can always invalid it by adding a dummy querystring parameter in the request url such as :
For ASP.NET server-side caching, you need to check how you define its refreshing or expire logic to make sure it will invalid/refresh whenever the certain condition occurs.
Also, I'd suggest you use fiddler or some other HTTP sniffer tool to inspect the HTTP request/response data to see if the response from server does match the expected caching behavior.