mvlcek Wrote:Maybe Apache is configured to send cache-Headers for php files.
Did you look at the headers sent from the server (e.g. via firefox plugin livehttpheaders or the network tab of firebug)?
Installed that addon earlier this morning and took a look. Problem is that I am not entirely sure what to look for.
So I scanned for mentions of cache and ran into this when I changed a bit of text, left the page, and went back to it:
Code:
If-Modified-Since: Fri, 27 Jul 2012 05:41:43 GMT
If-None-Match: "4315d34-f98-4c5c92abd73da"
Cache-Control: max-age=0
HTTP/1.1 304 Not Modified
Date: Sat, 28 Jul 2012 07:41:26 GMT
Server: Apache
Connection: Keep-Alive
Keep-Alive: timeout=5, max=98
Etag: "4315d34-f98-4c5c92abd73da"
Expires: Sun, 29 Jul 2012 07:41:26 GMT
Cache-Control: max-age=86400
Probably totally standard, but I did wonder when I saw cache-control: max-age=86400
But if mvlcek is right in that Apache is configured to send cache-Headers for php files, then basically the only party who can solve this is the provider, right?
By the way, if somebody wants to take a look you're more than welcome to, it's a test install in a sub folder so I can PM login details without any probs.
However, since the client doesn't mind moving provider I think that probably is the easiest solution in the end.