Quote:
Originally Posted by Miguel T
Most likely it's a load-balanced server, try getting the direct IP into your hosts file to debug quicker
|
you're right, if the JS file is behind a load balancer or CDN it might be getting cached server-side (it's not a browser-caching issue, OP)
it's part of why I'm in the habit of bumping the filename every time I update static resources, I just code my sites so there's only one file that references the actual resource URL and every other template includes the "common includes" template or whatever
there's a saying that there's only 2 hard problems in computer science: naming and cache invalidation. I mostly name my variables things like "fuck_you" and "your_mom_is_a_whore" so I'm not particularly opinionated as to the difficulty of naming things but when it comes to cache invalidation god DAMN I run into some tough issues