Network monitor doesn't handle NS_ERROR_NET_EMPTY_RESPONSE correctly
Categories
(DevTools :: Netmonitor, defect)
Tracking
(firefox138 fixed)
| 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.
Comment 1•9 months ago
|
||
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!
Comment 2•9 months ago
|
||
Nicolas, I can reproduce it with https://httpbin.org/status/404
| Reporter | ||
Comment 4•9 months ago
|
||
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 | ||
Comment 5•8 months ago
|
||
Updated•8 months ago
|
Comment 7•8 months ago
|
||
| bugherder | ||
Description
•