1325876 - Show internal error page for HTTP responses with error codes (4xx, 5xx) and "Content-Length: 0" instead of blank page

Status: NEW

(Core :: DOM: Navigation, defect)

Description

[Brad Lassey [:blassey] (use needinfo?)]

http://www.theworldin.com/article/12597/martin-luther-church-splitter?fsrc=scn/tw/wi/bl/ed/ didn't load

http://www.theworldin.com/article/12597/martin-luther-church-splitter does

Comment 1

[Wesley Huang [:wesley_huang] (EPM) (NI me)]

Using Chrome to open [1] gets HTTP ERROR 503 error. 

[1] http://www.theworldin.com/article/12597/martin-luther-church-splitter?fsrc=scn/tw/wi/bl/ed/

Comment 2

[Kevin Brosnan [Ex-Mozilla]]

Not a recent regression.

Comment 3

[Wesley Huang [:wesley_huang] (EPM) (NI me)]

(In reply to Wesley Huang [:wesley_huang] (EPM) (NI me) from comment #1)
> Using Chrome to open [1] gets HTTP ERROR 503 error. 
> 
> [1]
> http://www.theworldin.com/article/12597/martin-luther-church-
> splitter?fsrc=scn/tw/wi/bl/ed/

Server replies differently now. Now both chrome and firefox can load page thru the URL.

Comment 4

[Nevin Chen(Not active on Bugzilla)]

The website in comment 1 is normal now.
Julian gave me this website to test all the http status code: http://ozuma.sakura.ne.jp/httpstatus/
I've checked Chrome could display error message but we only show a blank page.

Comment 5

[James Willcox (:snorp) ([e-mail]) (he/him)]

I get this on desktop nightly too, so I think this might be intentional? Patrick, do we want show our internal load error pages if Content-length=0?

Comment 6

[Patrick McManus [:mcmanus]]

I think for the case of 0 bytes of content the front end should indeed show our local error page.. but if there is content then it probably makes sense to render it.

Comment 7

[Wesley Huang [:wesley_huang] (EPM) (NI me)]

So I guess the issue is not fennec specific. I'm changing the product/component.

Comment 8

[Sorina Florean [:sflorean]]

Hello and sorry for delay here. 

Tested with Huawei MediaPad M2 (Android 5.1.1) on latest Nightly (54.0a1 from 2017-01-29) and with page http://ozuma.sakura.ne.jp/httpstatus/ from comment 4.
Here are the results:
- http://ozuma.sakura.ne.jp/httpstatus/503 shows a blank page (same for 101, 200, 201, 202, 203, 206, 207, 208, 304, 305, 306, 400, 401 and the rest of the list)
- on Chrome I got the following message that page isn't working (http://ozuma.sakura.ne.jp/httpstatus/)
- the first link from description, is working in latest Nightly

Comment 9

[Julien Cristau [:jcristau]]

Too late for firefox 52, mass-wontfix.

Comment 10

[Manuel Bucher [:manuel]]

Using this bug to track showing error pages on http error responses with "Content-Length: 0", because it is the oldest I could find. Is there any specification which says that the browser should or may show an internal error page for http errors? In any case I think it would be less confusing for users instead of seeing an empty page.