Scenario
- You upload index-2-1.html to your website folder on uoregon.edu.
- In Chrome, you open http://pages.uoregon.edu/yourDuckID/110/index-2-1.html; it looks fine.
- In Sublime, you make some changes to index-2-1.html.
- You upload the modified version of index-2-1.html to uoregon.edu
- In Chrome, you open http://pages.uoregon.edu/yourDuckID/110/index-2-1.html, but you do not see your changes.
Problem
Your browser is showing you the version that it fetched from the server in step 2– that version is stored in the broswer’s cache memory, and that is what it shows you, so you do not see the changes you made to the web page.
Your changed version of index-2-1.html is actually on the server, you just have to tell Chrome to fetch the latest version.
Solution
Bypass your Browser’s Cache. Read the first page of this Wikipedia entry to learn the keyboard command that forces your browser to fetch the latest version of a web page from the server.
Notes
HTTP caching occurs when the browser stores local copies of web resources for faster retrieval the next time the resource is required.
When an item is fully cached, the browser may choose to not contact the server at all and simply use its own cached copy.
Example: Once CSS stylesheets are downloaded by the browser there’s no need to download them again during the user’s session. This holds true for many asset types like javascript files, images and even infrequently changing dynamic content. In these instances it is beneficial for the users browser to cache this file locally, and use that copy whenever the resource is requested again.