Mailing-List: contact modperl-help@perl.apache.org; run by ezmlm
Precedence: bulk
Received-SPF: pass (athena.apache.org: domain of pharkins@gmail.com designates
 209.85.217.19 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=message-id:date:from:sender:to:subject:cc:in-reply-to:mime-version
         :content-type:content-transfer-encoding:content-disposition
         :references:x-google-sender-auth;
        b=URjN03fwaeLR9UwCoitMV4LGbsTNsD6UZuk7SYtTO8l1lerfnjpw/tkIlG4j6+YrJz
         YZ3KIs9MmDt+7GMWuHbTWrAvy9/Cw1yXeOU3vlu8A4UxA0gC4TJ25qb/3jqri57U+quo
         CeZBpTSm/YX8MF70yAjIjcd94gbn037c6i5Wk=
Message-ID: <66887a3d0809021234s4d923c82o68deb885266fe762@mail.gmail.com>
Date: Tue, 2 Sep 2008 15:34:57 -0400
From: "Perrin Harkins" <perrin@elem.com>
Sender: pharkins@gmail.com
To: "Ashley Pond V" <ashley.pond.v@gmail.com>
Subject: Re: mp2, STDIN/POST is clobbered by CGI->new($r);
Cc: modperl@perl.apache.org
In-Reply-To: <A5D293AC-BE07-434A-8DDD-BD904F3E4705@gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <A5D293AC-BE07-434A-8DDD-BD904F3E4705@gmail.com>

On Fri, Aug 29, 2008 at 6:35 PM, Ashley Pond V <ashley.pond.v@gmail.com> wrote:
> How could you read the POST body without clobbering it to hand off to some
> PHP, or whatever is next in line?

I don't think you can.  Usually people use something like libapreq to
get around this, since it can just keep the parsed data and let you
use it across multiple phases, but that only works when everyone is
calling libapreq for their data.

- Perrin