> From: Arun Venkataraman [mailto:[EMAIL PROTECTED]]
> Sent: Thursday, August 24, 2000 9:28 PM
> You need to get familiar with the basics of HTTP. rfc 2068 is the ultimate
> authority in this regard.
RFC 2068 has been superceded by RFC 2616 since June 1999. (And it's a bit
misleading to say any RFC is "the ultimate authority" about anything, since
RFCs are subject to amendment, and hence are not "ultimate" in the proper
sense.)
> What happens is that the client submits a request say:
> GET /index.html HTTP/1.0. This will cause the server to terminate the
> connection after the request has been satisfied.
>
> If the client says:
> GET /index.html HTTP/1.0
> Connection: Keep-Alive
HTTP/1.0 has been superceded by HTTP/1.1, which is what RFC 2616 defines,
and what RFC 2068 defined before it. Persistent connections are a feature
of HTTP/1.1. (RFC 2068 notes that a few HTTP/1.0 implementations supported
persistent connections, but they are not part of the HTTP/1.0 specification,
which can be found in RFC 1945.)
The rules governing the HTTP-Version component of an HTTP request line are
detailed in RFC 2616, but to gloss a bit, an HTTP/1.1-compliant application
SHOULD use "HTTP/1.1" as its HTTP-Version, and MUST use "HTTP/1.1" if it
uses any features not compatible with HTTP/1.0 - such as persistent
connections.
Michael Wojcik [EMAIL PROTECTED]
MERANT
Department of English, Miami University
______________________________________________________________________
OpenSSL Project http://www.openssl.org
User Support Mailing List [EMAIL PROTECTED]
Automated List Manager [EMAIL PROTECTED]
