Return-Path: Delivered-To: apmail-httpd-modules-dev-archive@locus.apache.org Received: (qmail 94127 invoked from network); 13 Oct 2006 19:39:10 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 13 Oct 2006 19:39:10 -0000 Received: (qmail 27147 invoked by uid 500); 13 Oct 2006 19:39:09 -0000 Delivered-To: apmail-httpd-modules-dev-archive@httpd.apache.org Received: (qmail 27134 invoked by uid 500); 13 Oct 2006 19:39:09 -0000 Mailing-List: contact modules-dev-help@httpd.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: modules-dev@httpd.apache.org Delivered-To: mailing list modules-dev@httpd.apache.org Received: (qmail 27125 invoked by uid 99); 13 Oct 2006 19:39:09 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 13 Oct 2006 12:39:09 -0700 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received-SPF: neutral (asf.osuosl.org: local policy) Received: from [80.229.52.226] (HELO asgard.webthing.com) (80.229.52.226) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 13 Oct 2006 12:39:08 -0700 Received: from asgard (asgard [192.168.1.2]) by asgard.webthing.com (Postfix) with ESMTP id BD95E64559 for ; Fri, 13 Oct 2006 20:38:46 +0100 (BST) From: Nick Kew Organization: WebThing Ltd To: modules-dev@httpd.apache.org Subject: Re: Reading POST request without destroying it? Date: Fri, 13 Oct 2006 20:38:44 +0100 User-Agent: KMail/1.9.1 References: <20061013192621.GA2891@steve.org.uk> In-Reply-To: <20061013192621.GA2891@steve.org.uk> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200610132038.46293.nick@webthing.com> X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N On Friday 13 October 2006 20:26, Steve Kemp wrote: > Is there a simple way for my module to read/process the incoming > POST data, whilst still allowing the data to be passed on to > mod_cgi, etc? That's what input filters are for. How best to do it depends on the nature and size of the requests you're processing. -- Nick Kew Application Development with Apache - the Apache Modules Book http://www.prenhallprofessional.com/title/0132409674