Caching solution - is adding timestamp or random numbers at the end of file is acceptable?

Asked Mar 02 '17 at 10:49

Active Mar 02 '17 at 10:49

Viewed 1,188 times

I'm looking for a quick solution to fix caching issues (especially in Chrome but should include all modern web browsers).

Is appending timestamp or random numbers at the end of the file as a parameter good enough?

For example,

<script type="text/javascript" src="/somefile.js?123456789"></script>

where 12345678 is either a timestamp or randomly generated numbers.

In Developer tools, I can see that Chrome is not using local disk cache in this case.

DISCLAIMER

I understand there are better (proper) ways to solve this.

asked Mar 02 '17 at 10:49

iaforek

1

Answered here: http://stackoverflow.com/a/119056/7634537 – Fabian Klötzl Mar 02 '17 at 10:51
Perfect. Exactly what I was looking for. – iaforek Mar 02 '17 at 11:02
Possible duplicate of [How to force browser to reload cached CSS/JS files?](http://stackoverflow.com/questions/118884/how-to-force-browser-to-reload-cached-css-js-files) – iaforek Mar 02 '17 at 11:07
Marked as duplicate. Please close. – iaforek Mar 02 '17 at 11:08

0 Answers0