Emmanuel Revah wrote: > Dear Maintainer, Hello Emmanuel. I am not the maintainer but I have a suggestion. When you find strange things like this it is always good to double check using one of the command line tools. Note also that many sites have custom 404 pages that may be fooling you. Debian's site has custom 404 pages for example.
> It appears that Chromium does not let me see 404 pages sent from certain > websites. I've tested using the same website with Firefox, I get the usual 404 > header with the website's 404 page. > > With Chromium I do not, I get Chromium's own error page "No webpage was found > for the web address:". It would be good to double using wget or curl to verify the headers and return code completely independently of any of the web browsers. For example: $ wget -S -O/dev/null http://www.debian.org/testing-nonexistent --2017-05-16 18:27:25-- http://www.debian.org/testing-nonexistent Resolving www.debian.org (www.debian.org)... 149.20.4.15, 140.211.166.202, 128.31.0.62, ... Connecting to www.debian.org (www.debian.org)|149.20.4.15|:80... connected. HTTP request sent, awaiting response... HTTP/1.1 404 Not Found Date: Wed, 17 May 2017 00:27:25 GMT Server: Apache Content-Location: 404.en.html Vary: negotiate,accept-language TCN: choice X-Content-Type-Options: nosniff X-Frame-Options: sameorigin Referrer-Policy: no-referrer X-Xss-Protection: 1 Last-Modified: Mon, 08 May 2017 05:26:10 GMT ETag: "1e37-54efc7a13eacc;54f98ecd39bea" Accept-Ranges: bytes Content-Length: 7735 X-Clacks-Overhead: GNU Terry Pratchett Keep-Alive: timeout=5, max=100 Connection: Keep-Alive Content-Type: text/html Content-Language: en 2017-05-16 18:27:25 ERROR 404: Not Found. > I found one thing that does work: DevTools. Indeed, with devtools open I can > see the server's 404 page as I should. I do not understand what you mean when you say "with devtools open". But again I am not the maintainer but just another user. Bob
