> To clarify: HTTP 1.0 do not have persistent connection so "connection"
> has no meaning for HTTP 1.0 and server should drop connection after
> servicing such client request.
This is true under the official specification, but is not true as to how
the protocol is used. Persistent connections were used before they were
officially specified in HTTP 1.1. For example, Sun's JDK docs say "The JDK
supports both HTTP/1.1 and HTTP/1.0 persistent connections."
In practice, web servers *will* provide a persistent connection to
HTTP/1.0
clients that requeset one. For example:
$ telnet www.apache.org 80
Trying 192.87.106.226...
Connected to www.apache.org.
Escape character is '^]'.
>GET / HTTP/1.0
>Connection: Keep-Alive
HTTP/1.1 200 OK
Date: Mon, 17 Jul 2006 21:39:28 GMT
Server: Apache/2.2.0 (Unix) mod_ssl/2.2.0 OpenSSL/0.9.7g
Last-Modified: Sun, 09 Jul 2006 17:43:47 GMT
ETag: "20003-39aa-41829a3c27ac0"
Accept-Ranges: bytes
Content-Length: 14762
Cache-Control: max-age=86400
Expires: Tue, 18 Jul 2006 21:39:28 GMT
Keep-Alive: timeout=5, max=100
Connection: Keep-Alive
Content-Type: text/html
Notice the two persistent connection headers returned? And, in practice,
the connection is in fact persistent. If you were correct, the server would
ignore the "Connection" header since it "has no meaning". Try it without a
connection header and you will see the difference.
DS
______________________________________________________________________
OpenSSL Project http://www.openssl.org
User Support Mailing List openssl-users@openssl.org
Automated List Manager [EMAIL PROTECTED]
