httpd-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mathihalli, Madhusudan" <mad...@hp.com>
Subject RE: [PATCH] SSL not sending close alert message
Date Tue, 24 Feb 2004 04:25:56 GMT
Oh.. forget it - it was some setting in my browser :(
 
Thanks
-Madhu

________________________________

From: Mathihalli, Madhusudan
Sent: Mon 2/23/2004 3:16 PM
To: dev@httpd.apache.org
Subject: RE: [PATCH] SSL not sending close alert message



When I did a ssldump to analyze the default index.html access (using MSIE 6.0), it showed
that there were 3 requests and 3 connections - the session-id stayed the same. (dumb question:
) How did you manage the 2 requests on the same connection ?

-Madhu

-----Original Message-----
From: Joe Orton [mailto:jorton@redhat.com]
Sent: Monday, February 23, 2004 2:07 PM
To: dev@httpd.apache.org
Subject: Re: [PATCH] SSL not sending close alert message


On Mon, Feb 23, 2004 at 01:22:05PM -0800, Mathihalli, Madhusudan wrote:
> Hi,
>       I started working on Justin's idea of creating a EOC bucket - to
>       do a SSL shutdown before the socket close(). But since the
>       ap_flush_conn is called just before closing the socket - I
>       thought of doing the SSL shutdown during the flush itself. Let
>       me know what you think of this patch.

This is just back to what we had patches for already: doing an SSL
shutdown on any EOF bucket, right?  Which is not right since you get an
EOS after each HTTP response, not at the end of the connection.

Hence the need for a new bucket type to represent end-of-connection
differently from EOS.

(the test case for that is to see if you can send two requests on a
single SSL connection)

joe



Mime
View raw message