I was almost expecting this... ;)
This is not a browser application, I don't use forms. I see that there's no excuse not to use CGI on typical CGI applications, but in my project HTTP/CGI is merely a communications gateway (hehe, yes I know that HTTP/CGI is nothing more than that).
Besides that, using CGI would put me over the edge perfomance-wize. I'm under rapid fire from clients, and I need to be as lean as possible.
However, I don't want to start yet another use [no] CGI discussion, that wasn't my point in the first place. I simply wonder how setting $| nonzero could block those reads (!). To me that's something that simply must not happen (and under mod_cgi it does not happen)...
With "can't change my setup" I meant I can't update my Apache/mod_perl/OS (at least unless someone tells me that this is a bug that has been fixed in some later version, so I can apply pressure on the server/perl packaging folks -- I can understand they don't want to invest in AIX 4.3 any longer when we're migrating to AIX 5 anyway).So long,
Flexx
In reply to Re^2: mod_perl bug when reading post content with $|?
by Flexx
in thread mod_perl bug when reading post content with $|?
by Flexx
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |