Closed Bug 292941 Opened 20 years ago Closed 20 years ago

blazing fast back/forward doesn't work for sites that use cache-control: no-store

Categories

(Core :: DOM: Navigation, defect)

Product:
Core
Component:
DOM: Navigation
Platform:
x86
Windows 2000
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

()

Status:
RESOLVED INVALID

People

(Reporter: stevee, Unassigned)

References

Details

(Whiteboard: p-opera)

Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.8b2) Gecko/20050504 Firefox/1.0+ after landing of bug 274784 browser.sessionhistory.max_viewers 20 Apologies if this is expected behaviour. 1. Go to http://fileforum.betanews.com/ 2. Click a link. 3. Click back. Notice the page is loaded from the web, and is not blazingly fast. 4. Click forwards. Notice the page is loaded from the web, and is not blazingly fast.
Blocks: blazinglyfastback
No longer depends on: blazinglyfastback
Note that http://fileforum.betanews.com/ isn't cached at all according to Page Info (not a meta-header, it must be a http-header). Doesn't this force us to reload the page ?
Yeah the site includes those HTTP headers: Cache-Control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0 Pragma: no-cache Opera seems to ignore that and use the cache anyway, but i don't think we want to do that?
Seems to WFM. Have they removed cache control?
They did --- Cache-Control: private, must-revalidate, pre-check=0, post-check=0 Pragma: n/a --- (sorry about the double post)
Summary: blazing fast back/forward doesn't work for all sites → blazing fast back/forward doesn't work for sites that use cache-control: no-store
Whiteboard: p-opera
another link to use / testcase would be nice
This is by design. See https://bugzilla.mozilla.org/show_bug.cgi?id=112564 for more info -- we don't want to start getting blocked on various web sites.
Status: NEW → RESOLVED
Closed: 20 years ago
Resolution: --- → INVALID
*** Bug 298128 has been marked as a duplicate of this bug. ***
IMHO this is a bad decision, because mozilla can start being blocked by users, who will just use another browser. I know several people who prefer opera to mozilla because it's faster. Now, whith the new fast cache mozilla can finally match opera's speed, but the issue described in this thread makes this achievement nearly useless. P.S. And if "various web sites" really start blocking mozilla, it can be easily worked around. I think that usability of software should have a higher priority than politics. There should be at least an option to let the users cache what thay want and not what some broken websites want them to.
Component: History: Session → Document Navigation
QA Contact: history.session → docshell
You need to log in before you can comment on or make changes to this bug.