Geoffrey Sneddon wrote:
> ...
I think that we should have this in XHR. Basic summary is that Firefox
and Safari default to 200/OK; Opera defaults to 0/"" (but does not throw
INVALID_STATE_ERR); IE is inconsistent and sometimes gives 200/OK or
-1/some-random-value-from-the-HTTP-response. I think we should probably
just spec in XHR that 200/OK should be returned when there is no
status-code/reason-phrase.
We're fairly close to interoperability (as IE already sometimes does
it), and nothing matches the spec currently at all, I think it should be
put in XHR and not wait until my HTTP parsing spec, and waiting to see
if anyone will actually implement that.
...
An HTTP/1.1 response that does not contain a status line is invalid.
Please do not specify behavior that requires treating broken responses
as ok.
Speaking of which: do you have reliable data about why this would be
desirable?
BR, Julian
