I have a system where cache max-age is set to 0 and there is problem, when I have made some changes in my style.css fail the changes dont apear to client. Browser will use the old cached version of css.
I have simple question: Does naming css file as style.css?123 will be cached as a new?
I have a system where cache max-age is set to 0 and there is
Share
Yes, adding a unique query string to the resource’s URI will force the client to fetch a “fresh” version (since the client doesn’t know that it’s merely an update of a previously cached resource). This is known as fingerprinting and you typically use a timestamp or an incrementing version number1 of the CSS file.
Google Web Fundamentals has a great article on HTTP cache optimization. Especially the section titled “Invalidating and updating cached responses:”
Do note, that the fingerprint does not need to be a sequential number. Any value – hash, version, etc. – will do as long as the risk of collisions is limited.
1) This is what’s done here on SO, e.g.
http://sstatic.net/js/global-login.js?v=12