> I took a quick swing at putting one together but my mod_perl environment > is a bit screwed up right now. Can you see if it runs on your setup?
I don't know. I've run "perl ModPerl-Registry/t/cgi-bin/stdin.pl" and it (unsurprisingly) fails with a "Can't connect to localhost:8529", and I can't find in the docs what is the correct test invocation. The problem might not be always observable in real live setup because mod_perl and cgi can be in different process trees, but it will always emerge when the very first request server by apache is handled using mod_perl, and the second by cgi. My test setup contains this request in a file: POST /cgi-bin/modperl.cgi HTTP/1.1 Host: localhost Content-Type: application/x-www-form-urlencoded Content-Length: 13 Keep-Alive: 300 submit=Submit POST /cgi-bin/cgi.cgi HTTP/1.1 Host: localhost Content-Type: application/x-www-form-urlencoded Content-Length: 13 Keep-Alive: 0 Connection: close submit=Submit and it runs as httpd -X & nc localhost 80 < request killall httpd and the error is always reproducible. I don't know if the test suite can stop and start apache at will, but if yes, the test must do that before executing that stdin.t. -- Sincerely, Dmitry Karasik