Return-Path: Delivered-To: apmail-httpd-dev-archive@httpd.apache.org Received: (qmail 31562 invoked by uid 500); 10 Oct 2001 19:17:43 -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 31551 invoked from network); 10 Oct 2001 19:17:42 -0000 Date: Wed, 10 Oct 2001 12:17:21 -0700 From: Justin Erenkrantz To: dev@httpd.apache.org Subject: Placing a recent snapshot on daedalus? Message-ID: <20011010121721.P23667@ebuilt.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.22.1i X-AntiVirus: scanned for viruses by AMaViS 0.2.1-pre3 (http://amavis.org/) X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N Would it be possible to place a fairly current snapshot of httpd-2.0 up on daedalus? I'd really like to get the input filter changes hammered on. If it is broken, the sooner we get feedback, the better. I know that there are tons of other fixes (or "new features") that have entered recently that should also be tested in the "real world." I don't know if we can either place it on apache.org or put it on a different port, but with a log replay. I'll let those who do this sort of thing handle that. If it doesn't pass basic sanity tests (like the looping reads I just fixed), I'd like to know that as well. I know SSL is still broken and proxy may or may not be working (Ian?), but I don't believe that they are used by daedalus. I'm still frustrated with mod_ssl. I may just commit what I have so that others can possibly jump in here. I dunno what the right thing to do here is. Should I wait until it is perfect, or should I just commit what I have? (Remember, it is broken right now.) -- justin