Mailing-List: contact dev-help@httpd.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@httpd.apache.org
Date: Mon, 23 Feb 2004 22:07:08 +0000
From: Joe Orton <jorton@redhat.com>
To: dev@httpd.apache.org
Subject: Re: [PATCH] SSL not sending close alert message
Message-ID: <20040223220708.GA25574@redhat.com>
Mail-Followup-To: dev@httpd.apache.org
References: 
 <16A24B6050584143978000646801E93557BEE5@cacexc03.americas.cpqcorp.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: 
 <16A24B6050584143978000646801E93557BEE5@cacexc03.americas.cpqcorp.net>
User-Agent: Mutt/1.4.1i

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