Return-Path: Delivered-To: apmail-httpd-dev-archive@www.apache.org Received: (qmail 13996 invoked from network); 4 Jul 2004 21:03:53 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur-2.apache.org with SMTP; 4 Jul 2004 21:03:53 -0000 Received: (qmail 6570 invoked by uid 500); 4 Jul 2004 21:03:48 -0000 Delivered-To: apmail-httpd-dev-archive@httpd.apache.org Received: (qmail 6328 invoked by uid 500); 4 Jul 2004 21:03:39 -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 6139 invoked by uid 99); 4 Jul 2004 21:03:31 -0000 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests=FORGED_RCVD_HELO X-Spam-Check-By: apache.org Received: from [217.160.171.50] (HELO jupiter.hal-nine-zero-zero-zero.net) (217.160.171.50) by apache.org (qpsmtpd/0.27.1) with SMTP; Sun, 04 Jul 2004 14:03:29 -0700 Received: (qmail 14973 invoked from network); 4 Jul 2004 21:03:19 -0000 Received: from unknown (HELO news.perlig.de) (80.131.128.124) by jupiter.hal-nine-zero-zero-zero.net with SMTP; 4 Jul 2004 21:03:19 -0000 Date: Sun, 4 Jul 2004 23:03:18 +0200 From: =?ISO-8859-15?Q?Andr=E9?= Malo To: dev@httpd.apache.org Subject: Re: PROPOSAL: Enhance mod_headers as a debug/test tool Message-Id: <20040704230318.024eb90e@parker> In-Reply-To: References: Organization: TIMTOWTDI X-Mailer: Yes! Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-15 Content-Transfer-Encoding: quoted-printable X-Virus-Checked: Checked X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N * Nick Kew wrote: > (If this gets the thumbs up, I'll be happy to do the work:-) >=20 > In testing new code, it's often helpful to simulate different > browser requests, and responses. >=20 > For handlers and filters, mod_headers enables us to set up testcases > very easily, with the Header and (especially) RequestHeader directives. > But that's in a fixups hook, so it's no use for any hooks running in > earlier phases of a request. >=20 > My proposal is to introduce an additional DEBUG keyword to the > Header and RequestHeader directives. Headers marked as DEBUG will > be set in post_read_request, so they are available to other modules. > Without DEBUG, it will default to current (fixups) behaviour. >=20 > Of course, DEBUG won't work with conditional (Request)Header directives. > In addition to documenting this, attempts to do so will log a warning. Sounds like a good tool. comments from me: - I would not call it DEBUG, but "early" or "setearly" or the like - I'd just replace the env clause with that keyword (i.e. mutual exlusion) - post_read_request is *really* early. So these directives would be only va= lid in server context / virtual host. nd --=20 die (eval q-qq:Just Another Perl Hacker :-) # Andr=E9 Malo, #