When downloading a mar file handle additional networking error codes similar to how NS_ERROR_DOCUMENT_NOT_CACHED and offline are handled

NEW
Unassigned

Status

()

defect
P3
normal
3 years ago
2 months ago

People

(Reporter: rstrong, Unassigned)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

When analyzing telemetry data for bug 1284915 it became apparent that additional network errors should be handled similar to what was done in bug 1284915. Basically, if some of the mar file has already downloaded it should continue from where it left off.

Possible error codes to handle

                                      |       |  Count  |  Total  |
Network Error Code                    | Count | Percent | Percent |
--------------------------------------+-------+---------+---------+
NS_ERROR_UNKNOWN_HOST                 |   743 |  76.84% |   2.57% |
NS_ERROR_ABORT                        |    65 |   6.72% |   0.22% |
NS_ERROR_NET_INTERRUPT                |    36 |   3.72% |   0.12% |
NS_ERROR_CONNECTION_REFUSED           |    35 |   3.62% |   0.12% |
NS_ERROR_NET_RESET                    |    32 |   3.31% |   0.11% |
NS_ERROR_PROXY_CONNECTION_REFUSED     |    28 |   2.90% |   0.10% |
NS_ERROR_NET_TIMEOUT                  |    16 |   1.65% |   0.06% |
NS_ERROR_FAILURE                      |     7 |   0.72% |   0.02% |
NS_ERROR_NOT_AVAILABLE                |     5 |   0.52% |   0.02% |
--------------------------------------+-------+---------+---------+
All                                   |   967 | 100.00% |   3.34% |
Summary: Wen downloading a mar file handle additional networking error codes similar to how NS_ERROR_DOCUMENT_NOT_CACHED and offline are handled → When downloading a mar file handle additional networking error codes similar to how NS_ERROR_DOCUMENT_NOT_CACHED and offline are handled
Priority: -- → P2
Assignee: nobody → robert.strong.bugs
Status: NEW → ASSIGNED
Assignee: robert.strong.bugs → nobody
Status: ASSIGNED → NEW
Priority: P2 → P3
You need to log in before you can comment on or make changes to this bug.