Closed Bug 1949683 Opened 28 days ago Closed 18 days ago

Network monitor doesn't handle NS_ERROR_NET_EMPTY_RESPONSE correctly

Categories

(DevTools :: Netmonitor, defect)

defect

Tracking

(firefox138 fixed)

RESOLVED FIXED
138 Branch
Tracking Status
firefox138 --- fixed

People

(Reporter: jdescottes, Assigned: bomsy)

References

Details

Attachments

(2 files)

Will need to build a small test case, but it seems that DevTools network monitor doesn't handle the new NS_ERROR_NET_EMPTY_RESPONSE error correctly.

This status is used when browser.http.blank_page_with_error_response.enabled is set to false, when a 404/500 request has no content. Also leads to show a dedicated net error page instead of a blank page in case the request is a navigation request.

Julian, would you mind pointing to a page that does trigger this error?
We're not sure what the actual issue is here, are we missing a request in the netmonitor?

Thanks!

Flags: needinfo?(jdescottes)

Nicolas, I can reproduce it with https://httpbin.org/status/404

Thanks for the link Claas.

Flags: needinfo?(jdescottes)
Attached image image.png

To clarify, the issue is that we show the request as failed, whereas it should be a valid "404".
You can toggle browser.http.blank_page_with_error_response.enabled to true to compare the behavior.

Assignee: nobody → hmanilla
Status: NEW → ASSIGNED
Pushed by hmanilla@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/bf609adebfde [devtools] Add NS_ERROR_NET_EMPTY_RESPONSE to the list of platform errors which are ignored r=devtools-reviewers,nchevobbe
Status: ASSIGNED → RESOLVED
Closed: 18 days ago
Resolution: --- → FIXED
Target Milestone: --- → 138 Branch
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: