I have a real problem, and can't work it out.
By default, the C2 mobile project uses the offline.appcache feature which is supported by many browsers.
The problem is, once we have uplaoded one version,then delete the files and upload a new version of the game, we can only ever see the old version.
Getting the new version is proving to be a very difficult job.
In Safari on ihpone 4, ios 6, it never seens the new version, no matter how much refreshing you do.
Same with chrome on desktop, once you have an old version loaded, you wont get a new one.
but IE 10, always sees the new version.
I thought it was the apache web server caching the offline.appcache, but this doesnt seem to be the case. When My local chrome goes to the sites URL, using Charles proxy, I can see it gets the full and correct offline.appche, but kinds of ignores it. After it has read it once, the sever just sends 304 (not modified) response, which is correct.
In our office, we have one person with windows 7 who always sees the new version in all 4 browsers (IE, FF, Opera and chrome). We have another person who only ever sees the old version, which includes myself. so its not the ISP. In the office we have no proxy or caching.
On chrome, you dont seee the new version even if you "Empty the cache" from the tools menu, then go to the site again. you have to do this:
1) go to this URL: chrome://appcache-internals/
2) Find the site.
3) hit the remove button.
4) "empty the cache" in tools.
5) now when you go to the site, you will see the new version.
Safari on mobile is similar, requireing every user to go into settings->safari->Clear cookies and data.
We cant expect all our customers to do this each time, and have to mail them to tell them there is a new version.
On apache, I added this in the .htaccess:
AddType text/cache-manifest .appcache
If I modify any file on the Apache web server, then request it again, I seem to always get the latest version. The hosting company says they don't do any explicit caching in Apache.
But I think this was redundant, as the mime time which Apache is returning was that already.
If I run IIS locally, and deploy to that, I dont get the issue in Chrome or safari.
Any ideas? Anyone else with the same issue?
I cant tell if its a problem with:
1) the local PC
2) the ISP
4) windows chrome & safari on ios6