Closed Bug 884800 Opened 11 years ago Closed 7 years ago

Be more explicit about connection failures

Categories

(DevTools :: Console, defect, P3)

23 Branch
defect

Tracking

(Not tracked)

RESOLVED INVALID

People

(Reporter: djc, Unassigned)

Details

When requests fail to connect to the server (i.e. Unable to connect error page), the Console fails to make that easy to spot.

[14:55:42.647] GET http://127.0.0.1:10002/include.js [251ms]

It doesn't include any HTTP response code here, because there wasn't a response, but the timing for successful cases indicates that a response has been received. When clicking the console line, the Inspect Network Request dialog has an empty Status Code field, and shows the Request Headers, but no Response section. In other words, while you can deduce that the request has failed, both the console itself and the inspection dialog fail to make the failure explicit (let alone clarify the kind of failure).
OS: Windows 7 → All
Priority: -- → P3
Hardware: x86_64 → All
HTTP code is now included in the new console.
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → INVALID
Product: Firefox → DevTools
You need to log in before you can comment on or make changes to this bug.