UPDATE
Thanks for your anwers, monks!
Now this becomes even stranger... Since you guys think it sounds like a mod_perl bug, too, I installed mod_perl 1.26 and apache 1.3.23 on my SuSE 8.0 i686 Box, so I think I'm fairly up to date now.
Next I ran the client script against http://localhost/perl/tmp/echo_post_data.pl and guess what? It hangs with any content length I tried (1, 10, 10000, 11680, 11681, make your pick). Flip $| to zero, and data is flowing... %-|
It also works with mod_cgi (usually via /cgi-bin/), but it does not work with Apache::PerlRun (/cgi-perl/ on my box)
I'd really appreciate if somebody could crosscheck this on the same / other platforms.
I wonder how this can be a mod_perl bug. Am I the only one to use $| = 1 with mod_perl? 1.21 was out in 1998, how could this have been undiscovered until now?
You could break your CGI apps (or someone else's - HARHAR >;) with just one small change. Or, imagine a common CPAN module would start to set $| nonzero in a new verison... wow... 8|
So long,
Flexx
In reply to Re: mod_perl bug when reading post content with $|?
by Flexx
in thread mod_perl bug when reading post content with $|?
by Flexx
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |