Ranter
Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
Comments
-
C0D4669027yChrome is more relaxed if you append time stamps to the js / css files that are cached
I’ve found “main.js?t=23354”
Works well
The int being the last modified time stamp of the included file
Your profile suggests you do php, look at filectime() -
http://shouldiblamecaching.com is a good guide when to blame caching for a problem if your a web dev ;)
-
Thank you guys! Just learned php this month and your comments really helped me big time! 😀
-
C0D4669027y@iSwimInTheC doesn’t always clear cache.
Time stamp / file hash , based on file changes works as the cache is used unless the file changes, chrome sees it as a different file request -
Yes just like @JohnDoesNot says: open your dev console (you're developing anyways, right?) and disable cache on network tab, problem gone. It's not only chrome by the way, other browsers cache too.
Web dev prob:
When you modify a code then refresh your browser, It doesn't change anything and you think your code has the problem, Modifies 100+ lines and refreshed the page, still nothing happens. Asked someone about it, Fix? Fucking cache! Fuck you google chrome!
rant