[DeleGate-En] Re: SSL / keep-alive configure question
In message <_A2428@delegate-en.ML_> on 09/30/03(20:08:16)
you firstname.lastname@example.org wrote:
|./delegated -r -P10000 SERVER=https RELAY="no" FSV=sslway MOUNT="/*
|REMITTABLE="http" CACHE="no" RESOLV=dns
|The client connects to Delegate at port 10000 and Delegate initiates a
|SSL-connection to the remote server. For higher Performance I want to keep
|the connection to the remote SSL-server always alive, because the client
|sends many requests to delegate and IMHO the SSL-handshake for every
|request takes too much cpu-time. Is it possible to configure this (maybe
|with HTTPCONF=cka-cfi )?
The connection to a HTTPS server is kept alive during the connection from
a HTTP client is alive. So the necessary configuration is enabling
Keep-Alive or HTTP/1.1 capability of a HTTP client.
HTTPCONF=cka-cfi is not necessary for FSV, it only affect FCL and FTOCL.
|If this isn't possible, can Delegate/sslway re-use the SSL session-id?
|This would also help to prevent a new SSL-handshake at every request.
I have the plan to support it to avoid possibly multiple duplicate inquiries
for verification of a certificate (which needs manual verification of it)
on initial connection to a server.
D G Yutaka Sato <email@example.com> http://www.delegate.org/y.sato/
( - ) National Institute of Advanced Industrial Science and Technology (AIST)
_< >_ 1-1-4 Umezono, Tsukuba, Ibaraki, 305-8568 Japan
Do the more with the less -- B. Fuller