Have any of you guys noticed this? Chrome seems to be caching external php & javascript files regardless of headers...

for example... php headers for an external script, but they are still being cached locally.

header( 'Expires: Wed, 11 Jan 1984 05:00:00 GMT' );
header( 'Last-Modified: ' . gmdate( 'D, d M Y H:i:s' ) . ' GMT' );
header( 'Cache-Control: no-store' );
header( 'Pragma: no-cache' );

For once, everything works perfectly in IE & FF... however chrome caching these files is generating a major pain my asshole for every second real-time data updates. Have any of you encountered this problem or found a work around? even using JS and some random math for files hasn't fixed it. I have tried google but even 'php gurus' are pulling their hair out over it.

I remember dealing with this issue in 2007 with firefox... seems a bit retarded that it is happening in 2012 in chrome.

Put in a bug check with the chrome guys, they do respond, they are actually really good.

Some of the guys are saying this bug has been lodged for a -long- time and keeps getting looked over every release... I'll put another one in I guess.

you have to close chrome and do "ipconfig /flushdns" from the command prompt, then re-open chrome = fresh dns

Yes you do and it's annoying all the time (i swap dns's 3-4 times a day). At least i can turn chrome to restore closed tabs..

header('Last-Modified: '.gmdate('D, d M Y H:i:s').' GMT', true, 200);

Still no joy in chrome, I set up a bit of a simple test site to see if I can figure out what's going on... simple php script to load a random image from a folder, called using the php file as the img src.

Again, works perfectly in IE & FF, if you refresh, click a refresh page link and even using auto refresh headers loads a new image every time. Not in chrome though, stale information seems to get stuck in the cached script for about 1 - 2 minutes. CTRL + F5 loads a new image every time which still brings me to believe that chrome is just completely ignoring these headers.

Might just have to do a bit more research and see how other people are getting around this.

Chrome caches VERY aggressively compared to Firefox etc, I find.

Generally speaking if I CTRL-F5 two or more times directly in a row, it forces a cache refresh. In other browsers a CTRL-F5 is a signal to refresh everything all at once, but in Chrome it seems you have to do it a couple times in a row before it really decides to pay attention.

Another option is to hit CTRL-SHIFT-DELETE and you'll get a deletion dialog giving you options to delete cache. You can delete just for the last hour, which is handy for webdev stuff.

The problem is I can't tell every one else using the service to CTRL+F5 every few seconds if they use chrome lolol

some internets pages are telling me chrome caches POST requests differently, are you POSTing to this particular page?
can you try using GET instead?


I use GET for my dynamic graph pages and I've never had this problem, but it could just be a coincidence

I'll bugger around on the php image test site I whipped up and let you know the results, cheers for suggestion.

You can bust through all caches by doing a HTTP POST to the data source (even if you're just fetching data and really mean GET) as the proxy won't return a cached response.

I'd be surprised if that doesn't work for you.