Return-Path: Delivered-To: apmail-new-httpd-archive@apache.org Received: (qmail 31048 invoked by uid 500); 2 Aug 2001 23:14:30 -0000 Mailing-List: contact new-httpd-help@apache.org; run by ezmlm Precedence: bulk Reply-To: new-httpd@apache.org list-help: list-unsubscribe: list-post: Delivered-To: mailing list new-httpd@apache.org Received: (qmail 31028 invoked from network); 2 Aug 2001 23:14:30 -0000 X-Authentication-Warning: cobra.cs.Virginia.EDU: jcw5q owned process doing -bs Date: Thu, 2 Aug 2001 19:14:32 -0400 (EDT) From: Cliff Woolley X-X-Sender: To: Subject: Re: cvs commit: httpd-2.0/modules/tls mod_tls.c In-Reply-To: <1a7f01c11ba7$b703ea20$93c0b0d0@roweclan.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Spam-Rating: h31.sny.collab.net 1.6.2 0/1000/N Status: O X-Status: X-Keywords: X-UID: 72 On Thu, 2 Aug 2001, William A. Rowe, Jr. wrote: > Ok... after copious digging, I can't find any remaining errors that > would cause mod_tls and mod_ssl input filtering to misbehave, so I now > assume we have either a design flaw or a logic error. > > The mod_mime nonsense seems to be cleaned up, and after basing the NT > thread pool on the root pool, I seem to have eliminated all the > invalid memory references. Cool. > I'd still like to hold just a bit on 2.0.23 to see if we can't fix > mod_tls/mod_ssl form post acceptance. I'd imagine this same bug will > even bite us on overly large headers from the client (say, big > cookies.) +1... holding. -------------------------------------------------------------- Cliff Woolley cliffwoolley@yahoo.com Charlottesville, VA