404 http error isn't displayed in Firefox
Categories
(Core :: Networking: HTTP, defect, P2)
Tracking
()
People
(Reporter: yuri, Assigned: valentin)
Details
(Keywords: parity-chrome, Whiteboard: [necko-triaged])
Attachments
(1 file)
273 bytes,
application/x-javascript
|
Details |
User Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:74.0) Gecko/20100101 Firefox/74.0
Steps to reproduce:
I ran this NodeJS script always returning 404 http error:
const http = require('http');
const hostname = '127.0.0.1';
const port = 3009;
const server = http.createServer((req, res) => {
res.statusCode = 404;
res.end();
});
server.listen(port, hostname, () => {
console.log(Server running at http://${hostname}:${port}/
);
});
Actual results:
Firefox shows a blank screen.
(Chromium says HTTP ERROR 404)
Expected results:
Firefox should show the user a message about what happened.
The http code and other relevant info (the IP address, host name, headers) should also be displayed.
Reporter | ||
Comment 1•4 years ago
|
||
OS: FreeBSD 12.1
Comment 2•4 years ago
|
||
Could you please provide if it's possible a test page to try to reproduce the issue?
Thanks.
Comment 3•4 years ago
|
||
Because this bug's Severity has not been changed from the default since it was filed, and it's Priority is --
(Backlog,) indicating it has has not been previously triaged, the bug's Severity is being updated to --
(default, untriaged.)
Comment 4•4 years ago
|
||
Bugbug thinks this bug should belong to this component, but please revert this change in case of error.
Assignee | ||
Comment 5•4 years ago
|
||
Running the file with nodejs test.js
then loading http://127.0.0.1:3009/
shows an error page in Chrome and nothing in Firefox.
I guess it would be nice if we could provide some default content when there is none for a 404 response? It seems redirecting to about:neterror?something isn't the right approach here.
Assignee | ||
Updated•4 years ago
|
Assignee | ||
Updated•4 years ago
|
Updated•10 months ago
|
Description
•