5 ms·
does this have any impact on who does webdev and often substitutes resources reusing the same url or similar things?
by burnbabyburn 10y ago
does this have any impact on who does webdev and often substitutes resources reusing the same url or similar things?
- tyingq 10y agoSounds like it will, yes. You would have to open developer tools and "disable cache" on the network tab instead.
- deleted 10y ago[deleted]
- Nadya 10y agoLots more Ctrl+F5 to refresh instead of just pressing F5. It's actually been super annoying to explain to Project Managers - as they often don't see CSS changes due to this change (which actually happened nearly over a month ago).
- tokenizerrr 10y agoCtrl+Shift+R is a bit more ergonomic. > It's actually been super annoying to explain to Project Managers - as they often don't see CSS changes due to this change (which actually happened nearly over a month ago). You are appending a cachebuster to the URL that changes for every release, right?
- Nadya 10y ago>You are appending a cachebuster to the URL that changes for every release, right? I'm in a department with a many years outdated CMS. The modern CMS does this after minification. The version I'm stuck with doesn't do cache busting or minification. My department is stuck on the outdated CMS due to our necessary continued support of IE8. So unfortunately no, we're not. We do so manually once a site is in production but it isn't worth the effort to do manually while things are still fast moving and internal. It's much easier to occasionally remind the project manager that they need to do a hard refresh.
- tokenizerrr 10y agoThat sucks. If I was in your situation I'd look into having the webservers rewrite caching headers to just disable caching completely in the internal environment.
- chias 10y agoMy preferred solution to this is to generate links to resources like that (CSS, JS, etc) dynamically. For each filetype, set up your webserver such that `filename.[10-digits].css` is handled identically to `filename.css`. In apache, you can do this in .htaccess with a rule that looks something like: RewriteRule ^(.*)\.[\d]{10}\.(css|js|png)$ $1.$2 [L] Then generate your links by throwing the file's last modified timestamp into the URL. The net result is that if the file changes, the URL changes, and so the cache no longer applies. It's better than using a "fake" parameter (e.g. file.js?v=2) because using fake parameters suggests that the file is dynamic, causing browsers and proxies to behave differently.
- burnbabyburn 10y agoexactly this, there are people that need to access testing and could have this sort of problems.
- sp332 10y agoIf you have your cache control set correctly (short) for the resource, then the browser will still update it frequently.