728236 - HTML Pages are shown as text when served on nonstandard port with an HTTP status line starting "HTTP/0.9"

Status: RESOLVED WONTFIX

(Core :: Networking: HTTP, defect)

Description

[Andreas van dem Helge]

Attachment: invalid-rendering.png

User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:10.0.1) Gecko/20100101 Firefox/10.0.1
Build ID: 20120208060813

Steps to reproduce:

Visit a page that contains HTML


Actual results:

The HTML is shown as text, it is not rendered


Expected results:

The HTML should be rendered as such.

Comment 1

[Tim (fmdeveloper)]

Please capture the headers sent with the webpage (you can use Live Headers -> https://addons.mozilla.org/en-US/firefox/addon/live-http-headers/)

This is most often a request sent with incorrect headers

Comment 2

[Andreas van dem Helge]

You are probably right and I know it was about 7 releases prior but in versions from just a few months ago this was not an issue.

Comment 3

[Matthias Versen [:Matti]]

There is nothing that we can do without http headers from the addon, a Mozilla http log ->https://developer.mozilla.org/en/HTTP_Logging, a packet trace (wireshark) or a public URL

Comment 4

[Tim (fmdeveloper)]

Andreas -> Are you still hitting this? Have you been able to capture HTTP logging, or other diagnostic?

Comment 5

[Andreas van dem Helge]

Here is the requested header. It does not indicate any encoding of text or similar. Firefox is invalidly rendering HTML as text.

http://system.enterprise.local:81/

GET / HTTP/1.1
Host: system.enterprise.local:81
Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
Accept-Language: en-us,en;q=0.5
Accept-Encoding: gzip, deflate
DNT: 1
Cookie: PHPSESSID=f4cf0ac32dc995ae81b20fa28e4c0cdc
Connection: keep-alive

HTTP/0.9 200 OK
Expires: Fri, 18 May 2012 23:23:37 GMT

Comment 6

[Matthias Versen [:Matti]]

Are we still supporting http/0.9 ?
We may need a full packet trace as this could be a bug in the unknown content decoder.

Comment 7

[Boris Zbarsky [:bzbarsky]]

> Are we still supporting http/0.9 ?

Yes, on port 80.  Though note that the response header in comment 5 is not actually a valid HTTP/0.9 response (e.g. HTTP/0.9 doesn't have headers, or an HTTP status line).

But in this case the HTTP server using HTTP/0.9 is on a non-standard port (81 instead of 80).  We no longer sniff for HTML in that situation; see bug 667907.

However that bug was about cases that are valid HTTP 0.9 responses.  In this case, we've got the status line, which tells us that the server really is speaking HTTP (albeit in an incredibly broken way).  Patrick, could we just set the HTTP version to 1.0 internally when we see "HTTP/0.9"?  Seems like that would fix this particular page without affecting the fix for bug 667907 in the situations that matter.

Comment 8

[Patrick McManus [:mcmanus]]

Boris, I guess that would probably work. It would be a really low priority item to confirm it though and I'm not that excited about fixing support for invalid 0.9 especially if this is just a piece of home-grown brokenness.

Andreas, what is the server and can it be fixed?