[mp2] no STDIN for mod_cgi POST after ModPerl::Registry GET

[prev] [thread] [next] [Date index for 2005/05/27]

Hi,

I mailed a bug report with this same subject a few days ago.  I'm just
curious, does this sound like an unusual problem with my all of my builds, 
or is this kind of problem with STDIN common when serving mod_cgi and
ModPerl::Registry scripts from the same apache?

I found an old post with a similar-sounding mod_perl 1 problem here:
 http://aspn.activestate.com/ASPN/Mail/Message/modperl/1013538

Here's a short summary of my problem:
-------------------------------
I'm trying to run some ModPerl::Registry and some mod_cgi scripts on
the same server.  The problem is that sometimes the mod_cgi scripts
get no input for POST requests (STDIN is closed?).  I'm able to
reproduce it consistently like this:
 1. restart apache.
 2. do a GET request to a ModPerl::Registry script (with input).
 3. do a POST request to a mod_cgi script (with input).
   --> If the POST is served by the same child as the GET from step 2,
       the mod_cgi script doesn't see any input.  I can continue to
       re-POST to the mod_cgi script and repeat the problem.
(However, if I POST first to the mod_perl script, the mod_cgi script
works fine.)
I've reproduced this on multiple apache/mod_perl versions on solaris &
linux, and the results are the same no matter whether I use CGI.pm,
Apache2::Request, or read directly from STDIN:  the CONTENT_LENGTH is
correct but STDIN is empty.
-------------------------------

For now I've set up another apache with mod_proxy so that I can serve only
mod_perl from the one apache, but I'd like to be able to do it all from
one apache if possible.  Any ideas?

-Joe