in reply to Mod CGI problems with POST

Well ... what's on line 829 of CGI.pm (on my version 3.15 it's nothing). More than likely it's the line where $ENV{CONTENT_TYPE} is checked as to whether or not the data is application/x-www-form-urlencoded or multipart/form-data. Is that being sent by your client (or set by your server)?

-derby

Update: Normally that infinite loop in CGI is when CGI thinks it's in DEBUG mode and no GET nor POST data is sent (or none was recognized - bad content type) - it's waiting for input on STDIN.

Replies are listed 'Best First'.
Re^2: Mod CGI problems with POST
by cormanaz (Deacon) on May 31, 2007 at 01:19 UTC
    I've got ver 3.20 and lines 827 thru 831 are
    eval "package $pack; $code"; if ($@) { $@ =~ s/ at .*\n//; croak("$AUTOLOAD: $@"); }
    this is in sub _compile.

    If the content_type is as set by the FORM tag in the sample HTML file, the the content_type that comes through in the environment variable is multipart/form-data; boundary=---------------------------24805226817341 and the behavior is as I described with either the pattern match error or infininte wait if I debug. If I delete that parameter from the FORM statement the content_type is application/x-www-form-urlencoded and I get the infinite wait whether I run straight through or debug.