I'm trying to develop a strategy to handle cached javascript files, css, images, etc when we release an update to our site. Before I get into implementing version numbers on the javascript files I was wondering if an IIS reset after each release would effectively cause cached files to be resent.
Tell me more
×
Server Fault is a question and answer site for
professional system and network administrators. It's 100% free, no registration required.
|
When you do an IISReset the IIS cache will be cleared and then will start to be rebuilt after it starts back up as client requests come in. If you update a file then the older cached file will become stale and IIS will serve the updated file and update the cache with the new file. IISReset (although harsh) will clear the IIS cache but it won't do anything with local caches in proxies or clients. Maybe you've just got the terminology mixed up a bit, but there isn't any concept of "resent" when it comes to caching. It's all request based. If a client requests something and it's found in a cache then it'll get served from the cache. You'll need to force content expiration on your files if you will be maintaining the same filenames. |
|||||
|
|
No, client caching is based on content expiration time. |
|||
|
|
|
When you modify one javascript file, you need ALL clients what are running the web application to get the new file, it is clear to me the "recent". For each client to get from the server the new file, you only need to include in the include/script of your javascript in the web page the It is only necessary one parameter could be Example #1Example #2 |
||||
|
|
