Closed Bug 290624 Opened 20 years ago Closed 20 years ago

Reload page reads from cache

Categories

(Core :: Networking: Cache, defect)

x86
Windows XP
defect
Not set
normal

Tracking

()

RESOLVED INVALID

People

(Reporter: bugs.caleb, Assigned: darin.moz)

Details

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8b2) Gecko/20050416 Firefox/1.0+
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8b2) Gecko/20050416 Firefox/1.0+

It seems that when you press Reload, the page gets read from the cache again,
and to update it you'll need to clear the cache completely.

I am using AdMuncher (www.admuncher.com) which acts as a local proxy and
modifies every HTML page.

I have opened the same page in both IE and Firefox and then disabled AdMuncher.
I pressed refresh/reload in both browsers, and IE returned HTML code that was
not modified (because AdMuncher is disabled after all), but Firefox returned the
same, modified (outdated) code.

Reproducible: Always

Steps to Reproduce:
I'm pretty sure that's intended behavior. Use shift + reload to force it to pull
from the server.
if this happens with the reload button, I suppose it's right and intended

1.contextmenu in page reload
2.contextmenu on tab reload tab
3.ctrl+F5 (cmd+F5)

should all give a hard reload
Mozilla will use the cached version if the site reports that the content didn't
change. And in your case the content on the server didn't change.

You have to use shift+reload bypass the cache and reload from the server.

-> invalid (this is by design)
Status: UNCONFIRMED → RESOLVED
Closed: 20 years ago
Resolution: --- → INVALID
fwiw I suppose the proxy is broken (it probably passes the ETag through even
though it modified the content), but maybe it doesn't, not enough info to tell

anyway, reload sends if-modified-since/if-none-match headers, and yeah, the
server probably says "nothing changed" because well, nothing did change on the
server 
You need to log in before you can comment on or make changes to this bug.