Aggressive caching: do all browsers support the URL parameter for updating?

Question

With aggressive caching of CSS and other files, you can force the user to update the latest version of the stylesheet by renaming the file and contacting a new copy (for example, style.123.css is renamed to style.124.css ). Another method that is often used instead of renaming a file is to pass a URL parameter (for example, style.css? Ver = 123 , which will later be changed to style.css? Ver = 124 ).

Does all browsers support the latest method for downloading a new copy of the stylesheet? Are there any flaws in using the URL parameter to rename the file?

Answer 1

After further research, it turns out that some proxy caching services will not cache files with query strings in the URL. Whether this is true for some web browsers, I do not know.

Thus, this, apparently, is the only serious drawback of using query strings to update aggressively cached files - they may not be cached at all.

Answer 2

The only way the browser could not "support" caching with the control of request parameters was if the browser used the cached version obtained using a different parameter value. I have never heard of a browser that did this. So, all browsers support this technique. The only drawback I can think of is that you cannot host multiple versions of a resource at the same time. (if you are using static files)