I’ve believed that “hard refresh” means the browser ignores the cache to reload from the source. You might do so when you think a page has changed since you last viewed it.<\/p>\n
I made changes to a page, then pressed Ctrl-F5 for a hard refresh to see the alterations. The message “waiting for cache” actually popped up.<\/p>\n
“How could that be?” I asked myself. “Hard refresh is supposed to prevent the browser’s reaching to the cache.” It seems the browser was ignoring the “hard refresh” command. Was I mad?<\/p>\n
Apparently not: numerous other people report a similar experience. Some say that you must actually empty the cache to truly load the page afresh.<\/p>\n
Btw: as I recall, it mayn’t have been just one browser this happened with; at least two were behaving the same way, simultaneously.\n
Source:<\/p>\n
stackoverflow.com<\/a><\/p>\n fabricdigital.co.nz<\/a><\/p>\nJack of Oracle Tutoring by Jack and Diane,<\/a> Campbell River, BC.\n","protected":false},"excerpt":{"rendered":" Self-tutoring about home computer use: when hard refresh might have an unclear meaning. I’ve believed that “hard refresh” means the browser ignores the cache to reload from the source. You might do so when you think a page has changed …<\/p>\n