I'm asking in generalities - why would any server not set and return headers and/or status codes? I can't think of a good reason for this. Perhaps I'm overlooking something.
+6
A:
The Status-Code is a required part of a HTTP Response.
By definition, the only reason for a server not to provide a Status-Line is that it is not a HTTP server.
RFC 2616, section 6: Response.
Or said in a slightly less pedant way: if it does this, the server is hopelessly buggy and you should run away from it screaming.
ddaa
2008-10-16 18:32:53
Interesting...it appears that the PEAR HTTP classes do not proceed with an invalid security certificate...how they know that is beyond me, but I began checking the URLs that I'm looking at in a browser and so far, they all have an invalid certificate.
Thomas Owens
2008-10-16 18:36:32
A:
Status codes were introduced in HTTP/1.0 - prior to this, things were much simpler - there were no headers in the request or the response.
A request was simply like this, with no indication of the protocol version
GET /
The response would be all body, with no headers.
So it looks like you are talking to some kind of antique webserver which only speaks HTTP/0.9!
Paul Dixon
2008-10-16 20:32:57