you should judge the persistent connection by look up the http header. in http header,
it give the http version and etc, default, http version1.0 dont support persistent
connection, http version 1.1 support it.
By look up the header, the web server know whether shutdown the connection or not
after a REQUEST/RESPONSE.
If you program in middle ware of web server. there maybe exist the http version
information in enviroment that web server support.
-----原始邮件-----
发件人: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]代表 [EMAIL PROTECTED]
发送时间: 2000年8月25日 9:42
收件人: [EMAIL PROTECTED]
主题: re: using ssl in http protocol
a question about persistent mode in http
if in keep-alive mode, in the server side, how can i recongize a persistent connection
is shut down, and free the preserved resources of it? from the appearence of http
request and response, there seems on obvious steps to tell the server an persistent
connection will be terminated. and in the client side, i also can't find any
configuration about whether to choose keep-alive mode. then how the browser knows if i
want a persistent mode?
another question is: now, which web servers and browsers support persistent mode? i
wish there are some open source products i can refer to.
so many questions, thanks in advance.
-----T-J<O{O"------
4S#: "[EMAIL PROTECTED]" <[EMAIL PROTECTED]> 4z1m
"Arun Venkataraman" <[EMAIL PROTECTED]>
7"KM#: 2000Dj8TB25HU 1:03
JU<~HK#: "[EMAIL PROTECTED]" <[EMAIL PROTECTED]>
3-KM#: "[EMAIL PROTECTED]" <[EMAIL PROTECTED]>
VwLb#: Re: using ssl in http protocol
-----Original Message-----
From: [EMAIL PROTECTED] <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED] <[EMAIL PROTECTED]>
Date: Thursday, August 24, 2000 6:53 AM
Subject: using ssl in http protocol
>one question:
>http is a connectionless protocol(at least 1.0 is, and i don't know if
there are some implementations of http1.1). if we want to use ssl in http to
acquire secure connection, then, does it means we have to take the full
handshake for each connection(each request and reply)? if not, how they
implemented it then? are there some little source examples here(both client
and server)?
>Du Chunyan
[Moved to openssl-users]
If what you mean by a "connectionless" protocol is that there is no
mechanism for persistent connections, that is incorrect. HTTP/1.0 does
support persistent connections (using the Connection: Keep-Alive header) and
HTTP/1.1 does it by default.
Hence, if you are communicating to the same HTTPS server, upon a keep-alive
request, the server in most cases will oblige that request and keep the
connection open. However, that is the prerogative of the server.
Arun.
"If you torture data long enough, it will admit anything you want.."
****************************************************************
This message is for the named person(s) use only. It may contain
confidential, proprietary or legally privileged information. No
confidentiality or privilege is waived or lost by any mistransmission.
If you receive this message in error, please immediately delete it and
all copies of it from your system, destroy any hard copies of it and
notify the sender. You must not, directly or indirectly, use, disclose,
distribute, print, or copy any part of this message if you are not the
intended recipient. SPEEDERA NETWORKS, INC. reserves the right to
monitor all e-mail communications through its network.
______________________________________________________________________
OpenSSL Project http://www.openssl.org
User Support Mailing List [EMAIL PROTECTED]
Automated List Manager [EMAIL PROTECTED]
OkS5SPR;7]V;JtSZWT<:5D<r@zVz@mBp#?Gk8O?l5GB=KQ:|GsV0Vz@m#!http://career.sohu.com/index.html
KQ:|#:http://www.sohu.com
______________________________________________________________________
OpenSSL Project http://www.openssl.org
User Support Mailing List [EMAIL PROTECTED]
Automated List Manager [EMAIL PROTECTED]
______________________________________________________________________
OpenSSL Project http://www.openssl.org
User Support Mailing List [EMAIL PROTECTED]
Automated List Manager [EMAIL PROTECTED]
