Return-Path: Delivered-To: apmail-httpd-dev-archive@www.apache.org Received: (qmail 61374 invoked from network); 29 May 2004 13:31:40 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur-2.apache.org with SMTP; 29 May 2004 13:31:40 -0000 Received: (qmail 88022 invoked by uid 500); 29 May 2004 13:31:33 -0000 Delivered-To: apmail-httpd-dev-archive@httpd.apache.org Received: (qmail 87837 invoked by uid 500); 29 May 2004 13:31:32 -0000 Mailing-List: contact dev-help@httpd.apache.org; run by ezmlm Precedence: bulk Reply-To: dev@httpd.apache.org list-help: list-unsubscribe: list-post: Delivered-To: mailing list dev@httpd.apache.org Received: (qmail 87824 invoked by uid 99); 29 May 2004 13:31:32 -0000 Received: from [209.133.192.6] (HELO devsys.jaguNET.com) (209.133.192.6) by apache.org (qpsmtpd/0.27.1) with ESMTP; Sat, 29 May 2004 06:31:31 -0700 Received: (from jim@localhost) by devsys.jaguNET.com (8.11.7a/jag-2.6) id i4TDVSh11168 for dev@httpd.apache.org; Sat, 29 May 2004 09:31:28 -0400 (EDT) From: Jim Jagielski Message-Id: <200405291331.i4TDVSh11168@devsys.jaguNET.com> Subject: Re: 1.3.31 regression affecting Front Page? To: dev@httpd.apache.org Date: Sat, 29 May 2004 09:31:25 -0400 (EDT) Reply-To: jim@jaguNET.com In-Reply-To: from "William A. Rowe, Jr." at May 28, 2004 11:17:00 AM X-Mailer: ELM [version 2.5 PL5] MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N William A. Rowe, Jr. wrote: > > At 07:09 AM 5/28/2004, Jim Jagielski wrote: > >I've backed out that patch and asked Rasmus to send a replacemnet > >which addresses his specific problem but does not cause > >the below behavior. > > > >I'm tempted to release 1.3.32... > > Collect another week or few of data on other problems first, perhaps? > Once the replacement patch arrives - we have a home for this over > in /dist/httpd/patches/apply_to_1_3_31/, right? > > I'd also like to see a few other minor quibbles fixed, like the change > of canonical name behavior. I do have to wrap my head around that > issue still. > Well, I didn't mean immediately :) I do mean to release 1.3.32 much sooner than previous 1.3 versions have been released, like sometime in June. Although I'm still mulling over the UCN issue (and when/how to have Apache sort through the logic flow of how to "choose" the correct port number), there are other patches that would be beneficial to fold in, like the various ones you provided. -- =========================================================================== Jim Jagielski [|] jim@jaguNET.com [|] http://www.jaguNET.com/ "A society that will trade a little liberty for a little order will lose both and deserve neither" - T.Jefferson