Return-Path: Delivered-To: apmail-new-httpd-archive@apache.org Received: (qmail 84340 invoked by uid 500); 2 Jun 2000 23:04:48 -0000 Mailing-List: contact new-httpd-help@apache.org; run by ezmlm Precedence: bulk X-No-Archive: yes Reply-To: new-httpd@apache.org list-help: list-unsubscribe: list-post: Delivered-To: mailing list new-httpd@apache.org Received: (qmail 84325 invoked from network); 2 Jun 2000 23:04:44 -0000 Message-Id: X-Mailer: Novell GroupWise Internet Agent 5.5.3.1 Date: Fri, 02 Jun 2000 14:18:14 -0600 From: "Mike Gardiner" To: Subject: Re: 1.3.13 moving targets Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable Content-Disposition: inline X-Spam-Rating: locus.apache.org 1.6.2 0/1000/N OK OK I'll have the CHANGES to you shortly ;-) -Mike- >>> wrowe@lnd.com 06/02/00 12:52PM >>> Here's my shortlist of Win32 issues to fix before we roll: 1) Add a simple hold console open patch (wait for close or the ESC key, with a nice message) if the server died a=20 bad death (non-zero exit code) in console mode. Add the ConsoleHandler to deal with Ctrl+C/Ctrl+Break and, at least under NT, shutdown, logoff and window close. 2) Assure we haven't drifted too far between httpd.conf-dist and httpd.conf-dist-win. 3) Assure the windows.html and win_compiling.html reflect reality, today. 4) Get a CHANGES entry from Mike on the NW commit of=20 yesterday (nudge, nudge) That's three little things, but if someone wants to grab one and run with it be my guest! I've got the handle on the first issue myself, already. I'm sure some folk want to review the stat() success on failure scenario, to prevent other future holes from popping up there. Finally, is there any value in mod_proxy creating the ProxyRoot directory if it does not exist? If you think there is, what should the permission mask be (unix)?