Bug #793
closedProblem on FastCGI protocol when using TCP/IP and large POST data
Description
When submiting a form, POST method, with a large amount of data, the FCGI_STDIN record type has a wrong content length field.
To reproduce the problem :
1) Set up Lighty to use an external FastCGI server, configured like this (or similar to it) :
fastcgi.server = ( ".wsa" =>
(("host" => "127.0.0.1"
,"port" => 101
,"mode" => "responder"
,"check-local" => "disable"
,"allow-x-send-file" => "enable"
,"broken-scriptfilename" => "enable"
))
)
2) Put your backend server to run (and listen tcp/ip connections). Start lighty as well, of course.
3) Make a html form with a TEXTAREA. Important : POST method. Feed in a little bit of data (say 500 bytes) into the TEXTAREA and submit. It will go on OK.
4) Now enlarge that TEXTAREA by feeding say 80k characters. Submit and check how the external backend server will behave.
My understanding is that under these circumstances (large data), the content length field of FCGI_STDIN record is wrongly formatted.
Notice that I have made the same tests over Apache and it works OK. That is, same backend server, same html form, same amount of data. Everything works as expected.
When we switch to Lighty however, we have that problem on the content length field.
Also using Lighty either with GET or POST but smaller data, it works OK.
I'm running on Windows, although I think this problem will happen everywhere.
Thanks !
Updated by moo over 18 years ago
- Status changed from New to Fixed
- Resolution set to duplicate
dup #794
Also available in: Atom