Closed
Bug 20838
Opened 25 years ago
Closed 9 years ago
Conn: Unreachable server should cause cached data to be displayed
Categories
(Core :: Networking, enhancement, P3)
Tracking
()
RESOLVED
WONTFIX
Future
People
(Reporter: fur, Unassigned)
References
Details
In prior versions of Navigator, the cached version of a page was shown (with a warning dialog) if the origin server could not be contacted.
Comment 1•25 years ago
|
||
Mass move of all bugs without target milestones to M13.
Bulk move of all Cache (to be deleted component) bugs to new Networking: Cache component.
Comment 3•25 years ago
|
||
Assigning fur's cache bugs to Gordon. He can split them up with davidm.
Updated•25 years ago
|
Target Milestone: M13 → M14
Assigning to ruslan per warren's request.
Assignee: gordon → ruslan
Status: ASSIGNED → NEW
Target Milestone: M15 → M16
Comment 6•24 years ago
|
||
Moving to M17 which is now considered part of beta2.
Target Milestone: M16 → M17
I added some code (not enabled yet) which will return the cached response in cases when the connection can't be established with the Success serverity but with the original error code. The docshell needs to check for the error code and if it's there - pop-up the dialog box complaining about it.
Assignee: ruslan → travis
Status: ASSIGNED → NEW
Putting on [nsbeta2-] radar. Not critical to beta2. Assigning to valeski temporarily.
Comment 10•24 years ago
|
||
ruslan, is your code in? what code do we look for?
Whiteboard: [nsbeta2-]1d → [nsbeta2-]1d[nsbeta3-]
Comment 11•24 years ago
|
||
It's in and it can be enabled, but the docshell needs to display smth. Necko will just return cached copy.
Status: NEW → ASSIGNED
Comment 12•24 years ago
|
||
ruslan, how do we know when it's cached? check some status code on the channel?
Comment 13•24 years ago
|
||
-> gagan until we get a better idea of what to look for.
Assignee: valeski → gagan
Status: ASSIGNED → NEW
Comment 14•24 years ago
|
||
Clearing very old milestone (M17) in hope of reevaluation.
Target Milestone: M17 → ---
Comment 15•24 years ago
|
||
should be looked at after the new cache lands. ->neeti
Assignee: gagan → neeti
Target Milestone: --- → mozilla0.9.1
Comment 16•23 years ago
|
||
Darin, any suggestions on what to do with this bug? Do you know anything about what Ruslan put in place?
Comment 17•23 years ago
|
||
The correct/clean way IMHO is that we should intercept the errors propogated from the transport. currently we don't!-- we just let it send the error message directly to the progress listener handed in to the channel. So essentially we need a progress listener (in the channel) that we can hand over to the socket transport. once we get the notification of server not reached, we should turn around pop up the alert box and send data from the cache.
Comment 18•23 years ago
|
||
gagan: i agree
Comment 19•23 years ago
|
||
...but hasn't HTTP already truncated/doomed the old cache entry? Maybe not, if it was simply trying to validate the entry. Sounds like this is an HTTP issue, more than a cache issue.
Component: Networking: Cache → Networking: HTTP
Comment 20•23 years ago
|
||
moving to 0.9.2
Comment 21•23 years ago
|
||
*** Bug 75944 has been marked as a duplicate of this bug. ***
Comment 22•23 years ago
|
||
qa to me.
Severity: minor → enhancement
QA Contact: tever → benc
Summary: Unreachable server should cause cached data to be displayed → [RFE] Unreachable server should cause cached data to be displayed
Updated•23 years ago
|
Target Milestone: mozilla0.9.3 → mozilla0.9.4
Comment 23•23 years ago
|
||
*** Bug 100917 has been marked as a duplicate of this bug. ***
Comment 24•23 years ago
|
||
See also bug 28586, Should use placeholder error page, not dialog, for inaccessible pages.
Comment 25•23 years ago
|
||
This would be a nice improvement, and relatively simple to implement. Nominating for Mozilla 1.0 and nsbeta1.
Keywords: mozilla1.0,
nsbeta1
Comment 26•23 years ago
|
||
per adt, not critical for nsbeta1. hence minus.
Comment 27•23 years ago
|
||
+ conn - working on more detailed offline/online testcases.
Summary: [RFE] Unreachable server should cause cached data to be displayed → [RFE] Conn: Unreachable server should cause cached data to be displayed
Comment 28•22 years ago
|
||
moving neeti's futured bugs for triaging.
Assignee: neeti → new-network-bugs
Summary: [RFE] Conn: Unreachable server should cause cached data to be displayed → Conn: Unreachable server should cause cached data to be displayed
Comment 29•9 years ago
|
||
we do some different things in offline mode - which seems like the right plan for now
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → WONTFIX
You need to log in
before you can comment on or make changes to this bug.
Description
•