Return-Path: Delivered-To: apmail-modperl-archive@apache.org Received: (qmail 55686 invoked by uid 500); 16 Dec 2001 19:47:46 -0000 Mailing-List: contact modperl-help@apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: list-post: Delivered-To: mailing list modperl@apache.org Received: (qmail 55674 invoked from network); 16 Dec 2001 19:47:46 -0000 Message-ID: <001a01c1866a$8b9f1ac0$6401a8c0@charlotte> From: "Perrin Harkins" To: "Gerald Menzel" , References: <003d01c18198$c9fe8fc0$152ea8c0@gmpc01> <003101c18199$17ef9080$18020c0a@PerriHar> <003101c18621$7dc6d530$152ea8c0@gmpc01> Subject: Re: submit-data and chained handlers Date: Sun, 16 Dec 2001 14:47:48 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4807.1700 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4807.1700 X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N > Apache::RequestNotes don't work because Apache::Registry expect to read the > POST/PUT-data from STDIN. > > It's important that the cgi-scripts run unmodified and without any notice of > their "unnaturally" environment. I don't think there's any way around the fact that you can only read the content once. That means you need to read and store it for other handlers to use, which is what Apache::RequestNotes does. Alternatively, you could add something to your Registry script that stuffs the parsed values into pnotes yourself after using them. If you put that inside a block that checks for $ENV{'MOD_PERL'}, you'll still be able to run the script safely under standard CGI. It also looks like you're re-inventing Apache::Filter or Apache::OutputChain. Have you tried them? - Perrin