488664 - Should treat all HTTP/1.0 server responses as HTTP/1.1 for error correction

Status: RESOLVED INVALID

(Core :: Networking: HTTP, defect)

Description

[Yuxuan Wang]

User-Agent:       Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en; rv:1.9.0.8pre) Gecko/2009022317 Camino/2.0b2 (like Firefox/3.0.8pre)
Build Identifier: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en; rv:1.9.0.8pre) Gecko/2009022317 Camino/2.0b2 (like Firefox/3.0.8pre)

There're some (really stupid) server to claim the response is in HTTP/1.0, but actually it's in HTTP/1.1, e.g.:
http://my.donews.com/ifool/feed/

In the response:

HTTP/1.0 200 OK
...
Transfer-Encoding: chunked
...

Firefox (as of 3.1b3) didn't do the error correction, so the chunk header caused the XML to a parse error. Safari (4 beta) did it, so the XML was displayed correctly. IMHO it's a simple error correction, just treat it as HTTP/1.1, and it will works fine. And I didn't find any risk on doing it (please correct me if I'm wrong)

Reproducible: Always

Comment 1

[Masatoshi Kimura [:emk]]

This is intentionally ignored due to a fix for bug 330214 (or MFSA 2006-33).
http://www.mozilla.org/security/announce/2006/mfsa2006-33.html

Comment 2

[Matthias Versen [:Matti]]

marking invalid in that case, there are good reason to do it in that way as (comment#1) and why should the client fixed if this is a clear bug in the server ?