...
G.
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Darryl Miles
Sent: 15 August 2007 15:40
To: openssl-users@openssl.org
Subject: Re: Problem handling unexpected SSL shutdown
Shaw Graham George wrote:
The sequence of events goes like this:
1
Shaw Graham George wrote:
The problem is that, on Windows at least, my server doesn't appear to
get the SSL shutdown notify packet, for some reason. So, if that is
to be expected, I'm looking for an alternative way of detecting the
closure.
I've now tested it on Linux, and the existing code
handling unexpected SSL shutdown
Shaw Graham George wrote:
The problem is that, on Windows at least, my server doesn't appear to
get the SSL shutdown notify packet, for some reason. So, if that is
to be expected, I'm looking for an alternative way of detecting the
closure.
I've now tested
Shaw Graham George wrote:
Sure.
1. The server receives the HTTP request, using SSL_read() and
SSL_pending(). The request contains a Keep-Alive request.
2. The server writes the data out to another process.
3. The server then it sits on an event handler that multiplexes a
select() (or
Side track: Is it possible to make the window platform listen on 31
sockets at once per thread ? (or whatever is small limit was)
IOCP.
Okay you closed your ears to the read event ? On Unix the select() has
an exceptfds which can be used to pickup a socket error/close (but may
not be
Some more information and thoughts.
I can replicate the server behaviour using openssl s_client, sending the
HTTP request, and then shutting down the client with a Q.
I'm wondering if the problem is that, once the HTTP request is received
by my server, then it has no read interest in the socket
Shaw Graham George wrote:
Hi,
We have an application that provides HTTPS, either as client or server,
for our customers. At the moment I am doing some testing between our
client and our server, as a result of a problem with one of our
customers, and there is a particular sequence of
jimmy bahuleyan wrote:
Shaw Graham George wrote:
Hi,
We have an application that provides HTTPS, either as client or server,
for our customers. At the moment I am doing some testing between our
client and our server, as a result of a problem with one of our
customers, and there is a
Of jimmy bahuleyan
Sent: 15 August 2007 14:01
To: openssl-users@openssl.org
Subject: Re: Problem handling unexpected SSL shutdown
jimmy bahuleyan wrote:
Shaw Graham George wrote:
Hi,
We have an application that provides HTTPS, either as client or
server, for our customers. At the moment I am doing
Shaw Graham George wrote:
The sequence of events goes like this:
1. The SSL handshake proceeds as normal.
2. The client puts an HTTP request
3. The server gets the HTTP request
4. The client then executes an (unexpected) SSL shutdown
5. The server puts the HTTP response
Here I might
10 matches
Mail list logo
