I found that CGI.pm doesn't work quite as I would have expected in our
implementation of it. We are temporarily using PerlRun while we re-write
some of this code to work efficiently under ModPerl2.
Under PerlRun, when taking these steps:
1. Have a form POST to a script
2. Have that script redirect the user via GET to another script
using a relative path to the same virtual host
3. Have that new script attempt to parse the QUERY_STRING data via
CGI.pm and the results from CGI.pm do not match the ENV's QUERY_STRING value
Because of this I was guessing that maybe CGI.pm is not what one should be
using with ModPerl2 - but this could just be the situation when using
PerlRun.
Thanks everyone for the advice!
-----Original Message-----
From: Perrin Harkins [mailto:[EMAIL PROTECTED]
Sent: Thursday, August 31, 2006 2:09 PM
To: Kevin A. McGrail
Cc: [EMAIL PROTECTED]; modperl@perl.apache.org
Subject: Re: Receiving user input
On Thu, 2006-08-31 at 12:45 -0400, Kevin A. McGrail wrote:
> Attached is our function that we use both under mod_perl and standard
> perl.
No offense, but you'd be much better off using one of the standard
parsers, like CGI.pm or libapreq. These get a lot of peer review and
the bugs have been pretty well shaken out over the years. If you think
it's easy to get these things right, take a look at the CGI.pm
changelog.
- Perrin
