Question

74

Cache busting via params

rated 0 times [ 80] [ 6] / answers: 1 / hits: 126378 / 12 Years ago, tue, march 13, 2012, 12:00:00

We want to cache bust on production deploys, but not waste a bunch of time off the bat figuring out a system for doing so. My thought was to apply a param to the end of css and js files with the current version number:

<link rel=stylesheet href=base_url.com/file.css?v=1.123/>

Two questions: Will this effectively break the cache? Will the param cause the browser to then never cache the response from that url since the param indicates that this is dynamic content?

Answers

Only authorized users can answer the question. Please sign in first, or register a free account.

ryder

Add To Favorites

Follow

Total Points: 473

Total Questions: 110

Total Answers: 91

Location: Northern Ireland

Member since Mon, Nov 14, 2022

2 Years ago

answered 12 Years ago alli · Accepted Answer

The param ?v=1.123 indicates a query string, and the browser will therefore think it is a new path from, say, ?v=1.0. Thus causing it to load from file, not from cache. As you want.

And, the browser will assume that the source will stay the same next time you call ?v=1.123 and should cache it with that string. So it will remain cached, however your server is set up, until you move to ?v=1.124 or so on.