[Pkg-chromium-maint] Bug#862752: chromium: 404 pages can't be found

[Emmanuel Revah]

On 2017/05/17 02:27, Bob Proulx wrote:
> Emmanuel Revah wrote:
>> Dear Maintainer,
> 
> Note also that many sites
> have custom 404 pages that may be fooling you.

I'm not sure what you mean. In my case, this is my own website, when a 
page doesn't existe I send a 404 header and a message explaining that 
the page does not exist. It's quite possible that I've not done this 
correctly.


>> 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.


$ wget -S -O/dev/null https://mysite.example.com/non-existant
[...]
HTTP request sent, awaiting response...
   HTTP/1.1 404 Not Found
   Date: Wed, 17 May 2017 07:26:01 GMT
   Server: Apache
   Expires: Thu, 19 Nov 1981 08:52:00 GMT
   Cache-Control: no-store, no-cache, must-revalidate, post-check=0, 
pre-check=0
   Pragma: no-cache
   Refresh: 0; url=/blah/en/404
   Set-Cookie: Blah=5d5ohc17apk5dmhaobu4l7pj62; path=/
   Vary: User-Agent
   Cache-Control: max-age=290304000, public
   X-Content-Type-Options: nosniff
   X-XSS-Protection: 1; mode=block
   X-Frame-Options: sameorigin
   X-Powered-By: kittens
   Content-Length: 0
   Keep-Alive: timeout=5, max=100
   Connection: Keep-Alive
   Content-Type: text/html; charset=UTF-8
2017-05-17 09:26:01 ERROR 404: Not Found.


I tried with my website, what are we looking for exactly ? Is it 
Content-Length (is this a case of PEBKAC ?) ?


>> 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.


When I press "F12" a window opens up with developer tools, while this is 
open I get the expected 404 pages served from the web server.


Cheers,


Manu