Predictable Caching: Today's oxymoron

Permalink
AAAAAARRRRRRGGGGGHHHHHHH.

I have a custom block that's part of a package, which has its own view.css file.

The problem: when I deploy a new version of view.css to my host (iPage), the page still displays using the prior version.

I had this last week, and after poking & prodding it, it started working - I suspect it wasn't something I did, but who knows.

So today, I'm back with this same problem. Here's what I've tried:
- iPage has a cache control - I've turned off all caching.
- C5 has cache control - i've turned off all caching, and cleared the cache.
- Using Firefox - I've cleared it's cache.

And no matter what, reload the page, and it's still got the old version of the CSS.

On a five-point (5-high) scale, my knowledge/experience with C5 is maybe 2, css <1, though I've been a software developer for ages so I've got the analytical chops - but i've hit a wall with this caching business.

Also - what makes this even more annoying, is that when I run my local site (WAMP), everything reloads fine. Switch to another tab to the iPage-hosted page, and zero-zip-nada.

All suggestions gratefully accepted!!!

ssdscott
 
rvdbedum replied on at Permalink Reply
This really sounds like server caching as in opcache or something like that. Mostly you can find some useful information about caching in the headers of the requested file. Look for Most hosting providers use file caching to lower there load on there file storage.

In case of server file caching you can try to add an hash to the css file like ?refresh=timestamp
ssdscott replied on at Permalink Reply
ssdscott
Thank you - I will give that a try & let you know how it turns out.