[FASTCGI] can FCGI_STDIN content length be increased when receivingthe STDIN data?
i_konstantin at yahoo.com
Fri Dec 11 22:52:38 EST 2009
Thanks for the comments. First I wanted to correct myself when I said STDIN, it is actually the data that comes from FCGI_STDOUT. Secondly, I am not using the Apache server, I am using the custom server.
From: Martin Chapman <chapmanm at pixia.com>
To: Konstantin Ivanov <i_konstantin at yahoo.com>; fastcgi-developers at mailman.fastcgi.com
Sent: Fri, December 11, 2009 7:43:22 PM
Subject: RE: [FASTCGI] can FCGI_STDIN content length be increased when receivingthe STDIN data?
It might be a limit of Apache server with
their bucket brigade buffer sizes. This define is in apr_buckets.h and I
know that mod_fastcgid uses a bucket brigade to stream IO. Maybe there is
an Apache config setting in httpd.conf to increase the limit.
/** default bucket buffer size - 8KB minus room for memory
allocator headers */
From:fastcgi-developers-bounces+chapmanm=pixia.com at mailman.fastcgi.com
[mailto:fastcgi-developers-bounces+chapmanm=pixia.com at mailman.fastcgi.com] On Behalf Of Konstantin Ivanov
Sent: Friday, December 11, 2009
To: fastcgi-developers at mailman.fastcgi.com
Subject: [FASTCGI] can FCGI_STDIN
content length be increased when receivingthe STDIN data?
Hi all, I have the
following situation which I am try to bypass in attempt to increase the
performance. I am using PHP (php-cgi) in FCGI mode on Windows. I have a client
to read from the fastcgi server written in C++. The "issue" I am
experience is the size of the STDIN content length. I have a file of 65000
bytes (actually it is a print from php-info() function), but when I read it
from the FastCGI process the STDIN type header always comes back with the
maximum of 8184 bytes, which means that in order to read the entire request and
before receiving FCGI_END_REQUEST i have to loop and read from the socket fd 8
times. I think that this is very inconvenient and I was wondering what
controls the STDIN maximum content length? You see, if one would increase the
Windows socket window size to say 128Kb, then the request of 65000 bytes could
be read with a single iteration to recv() function. Did anyone experience the
same behavior and if so, would you please give your advice or point in the
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the FastCGI-developers