|
|||||||||||
|
Re: 1.1b3 and things???
From: Alexei Kosut <akosut(at)nueva.pvt.k12.ca.us>
Date: Sun Jun 09 1996 - 13:37:22 EDT
> Hmmm... I'm not sure this is really a problem. "Connection: Keep-alive"
Probably true. But I don't think we should send it. (saves us 23 bytes per request at any rate). > HTTP/1.1 clients *do* have to be special-cased, since the absence of
Nope. Think about it; at least, think about it the way I'm thinking about it (which may not be correct): I'm a HTTP/1.1 client. I don't understand any of that HTTP/1.0 Keep-Alive stuff, I just know the HTTP/1.1 version. I send a request, tagged with HTTP/1.1, to a server. This server is an Apache that understands HTTP/1.1 persistent connections, but calls itself a HTTP/1.0 server. Now, what do I get back? HTTP/1.0 200 OK
There's nothing in there that suggests a persistent connection. There's the Content-length, but that's not an indication - a lot of non-persistent servers send those, and there are HTTP/1.0 servers out there that send incorrect content-lengths. We're not allowed to trust them. The server *has* to assume that we don't support persistent connections, because there's no way it could know that we do. So it waits for the connection to close, which it never does. Oops. The only way it could have known is if we tagged ourself as HTTP/1.1, which, just like on the client side, says "this connection should be persistent unless otherwise stated". I don't see any way around this... -- ________________________________________________________________________ Alexei KosutReceived on Sun Jun 9 10:37:40 1996 This archive was generated by hypermail 2.1.8 : Thu Aug 24 2006 - 14:43:35 EDT |
||||||||||
|
|||||||||||