(Educators, a student account is needed to work in Mastering standard’s Mobile view.) Note that you may need to return to your computer to complete some assignments or assignment items. Supported browsers are listed above. The Kindle is not supported.
I stumbled across this question and was skimming through answers. This is a terrible idea, because: 1) generating the random number at every request will cause browsers to re-download the file at every visit. You want a build time value, so that browsers only regenerate the value when you make changes to the site. Since PHP is runtime interpreted, you might need to do it at deploy-time instead.
And 2) generating a random number means that sometimes (with the probability increasing over time), the browser will some random old cached copy. If you must do it at request time, use a timestamp!
– Jun 18 '18 at 20:10. A few ideas:. When you refresh your page in Chrome, do a CTRL+F5 to do a full refresh. Even if you set the expires to 0, it will still cache during the session. You'll have to close and re-open your browser again.
Make sure when you save the files on the server, the timestamps are getting updated. Chrome will first issue a HEAD command instead of a full GET to see if it needs to download the full file again, and the server uses the timestamp to see.
If you want to disable caching on your server, you can do something like: Header set Expires 'Thu, 19 Nov 1981 08:52:00 GM' Header set Cache-Control 'no-store, no-cache, must-revalidate, post-check=0, pre-check=0' Header set Pragma 'no-cache' In.htaccess. The problem is that Chrome needs to have must-revalidate in the Cache-Control` header in order to re-check files to see if they need to be re-fetched. You can always SHIFT-F5 and force Chrome to refresh, but if you want to fix this problem on the server, include this response header: Cache-Control: must-revalidate This tells Chrome to check with the server, and see if there is a newer file. IF there is a newer file, it will receive it in the response. If not, it will receive a 304 response, and the assurance that the one in the cache is up to date. If you do NOT set this header, then in the absence of any other setting that invalidates the file, Chrome will never check with the server to see if there is a newer version.
Here is a that discusses the issue further. I was getting the same css file when I browse website(on hosting company server with real domain) and I was unable to get the updated version on chrome. I was able to get the updated version of the file when I browse it on Firefox. None of these answers worked for me. I also have the website files on my machine and browse the site with localhost using my local apache server. I shut down my apache server and I was able to get the updated file.
![Please Please](/uploads/1/2/5/4/125465542/314664048.png)
Somehow my local apache server was messing with the chrome cache. Hope this helps someone as it was very hard for me to fix this.