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.
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.
Assigning fur's cache bugs to Gordon. He can split them up with davidm.
Seems non-essential for beta. Moving to M15.
Assigning to ruslan per warren's request.
Moving to M17 which is now considered part of beta2.
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.
Um, details on where this error is returned from?
Putting on [nsbeta2-] radar. Not critical to beta2. Assigning to valeski temporarily.
ruslan, is your code in? what code do we look for?
It's in and it can be enabled, but the docshell needs to display smth. Necko will just return cached copy.
ruslan, how do we know when it's cached? check some status code on the channel?
-> gagan until we get a better idea of what to look for.
Clearing very old milestone (M17) in hope of reevaluation.
should be looked at after the new cache lands. ->neeti
Darin, any suggestions on what to do with this bug? Do you know anything about what Ruslan put in place?
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.
gagan: i agree
...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.
moving to 0.9.2
*** Bug 75944 has been marked as a duplicate of this bug. ***
qa to me.
*** Bug 100917 has been marked as a duplicate of this bug. ***
See also bug 28586, Should use placeholder error page, not dialog, for inaccessible pages.
This would be a nice improvement, and relatively simple to implement. Nominating for Mozilla 1.0 and nsbeta1.
per adt, not critical for nsbeta1. hence minus.
+ conn - working on more detailed offline/online testcases.
moving neeti's futured bugs for triaging.
we do some different things in offline mode - which seems like the right plan for now