Open
Bug 665275
Opened 15 years ago
Updated 3 years ago
Cache of github issues page is consistently out of date until explicitly refreshed
Categories
(Core :: Networking: Cache, defect, P3)
Tracking
()
NEW
People
(Reporter: jdm, Unassigned)
Details
(Whiteboard: [necko-backlog])
Attachments
(1 file)
|
1.50 MB,
text/plain
|
Details |
This bug occurs like clockwork for me on nightlies.
STR:
1. go to https://github.com/graydon/rust/issues?sort=created&direction=desc&state=open
2. click on any issue
3. go back
Expected:
The same view as step 1 results (allowing for any changes that occurred whilst viewing the issue).
Actual:
The view is a cached one from the last time I visited the page.
Comment 1•15 years ago
|
||
> 3. go back
How? If using the back button, the expectation is that the cached version will be shown on history navigations....
| Reporter | ||
Comment 2•15 years ago
|
||
I use command+left brace on my mac, which is presumably the same action as the back button. I don't understand why the page I was just at wasn't cached, and I see the cached version from the previous day instead. Should I grab an nspr log of this?
Comment 3•15 years ago
|
||
> I don't understand why the page I was just at wasn't cached, and I see the
> cached version from the previous day instead.
Oh, I see. That sounds pretty broken, yes.
If you can reproduce reliably, an HTTP log would be interesting, yes.
| Reporter | ||
Comment 4•15 years ago
|
||
Here's a big honkin' log starting from when I first go to the issues page. The relevant urls to help you find your bearings are https://github.com/graydon/rust/issues, https://github.com/graydon/rust/issues/536, and https://github.com/graydon/rust/issues?sort=created&direction=desc&state=open.
Comment 5•15 years ago
|
||
Hmm. So from HTTP's point of view, we just use "HTTP:https://github.com/graydon/rust/issues?sort=created&direction=desc&state=open" as a cache key, get a cache entry, and read it.
That's the first request for that URI in the log (which has VALIDATE_NEVER). The second one has VALIDATE_ALWAYS and rereads from the server....
Updated•10 years ago
|
Whiteboard: [necko-backlog]
Comment 6•8 years ago
|
||
Bulk change to priority: https://bugzilla.mozilla.org/show_bug.cgi?id=1399258
Priority: -- → P1
Comment 7•8 years ago
|
||
Bulk change to priority: https://bugzilla.mozilla.org/show_bug.cgi?id=1399258
Priority: P1 → P3
Updated•3 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•