Closed Bug 47467 Opened 25 years ago Closed 25 years ago

'Back' gave me a page from a week ago

Categories

(Core :: Networking: Cache, defect, P3)

Product:
Core
Component:
Networking: Cache
Platform:
x86
FreeBSD
Type:
defect

Tracking

()

Status:
VERIFIED WORKSFORME

People

(Reporter: jesup, Assigned: neeti)

References

(
URL
)

Details

I went to slashdot.org (shortly after starting mozilla). The page came in just fine (up-to-date data, Aug 3rd). I clicked on an article, and read it. I hit back. The page that was shown to me was a copy of http://slashdot.org I'd read (in mozilla) about a week ago (since they articles are dated, I could tell it was July 25). Hitting forward and back, or back and forward still left me with the July 25th version. Reload produced the correct version. The article I clicked on was http://slashdot.org/article.pl?sid=00/08/03/0546224&mode=nocomment not that it matters I think. Testing this would require going to slashdot, seeing the page, waiting until something new is added to slashdot, and then seeing if this can be made to happen. Sounds like a cache bug to me.
Randall, Which build were you using? I checked in a fix for this on 8/1/00 for bug 40449. Neeti
Fresh pull Aug 1 circa 11am EDT. I'll update again.
I checked in my fix on Aug 1 at around 3:00 pm PST. Neeti
Pulled current source 8/3/00: The problem seems to have gone away; though it's hard to be 100% sure. Go ahead and close the bug, and if I hit it again I'll reopen. Thanks
This bug is still there; I see it on CNN's home page now. Fresh pull/build on 8/13/00. I'd left it on CNN yesterday. Today I reloaded, went to a few other pages, and went back to CNN, and the page was again page from yesterday.
Status: UNCONFIRMED → NEW
Ever confirmed: true
I cannot reproduce the problem. Here are the steps I followed. 1. Go to http://www.cnn.com. Page was "Updated 12:59 p.m. EDT." 2. Reloded the page after a few minutes. Page was "Updated 01:05 p.m. EDT" 3. Clicked on a link. 4. Pressed the back button. Got the cnn home page Page was "Updated 01:05 p.m.EDT" Neeti
The problem has never seemed to be trivially repeatable; the two cases reported are the two times I noticed it happening. I'll keep watching for it.
Closing out since I haven't seen this bug in a few weeks of watching. Will reopen if it happens again. Hopefully it's been fixed.
Status: NEW → RESOLVED
Closed: 25 years ago
Resolution: --- → WORKSFORME
verified by reporter
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.