> The main issue with FastCGI connection multiplexing is lack of flow
control.
Suppose a client stalls but a FastCGI backend continues to send data to it.
At some point nginx should say the backend to stop sending to the client
but the only way to do it is just to close all multiplexed connections
The FastCGI spec has some fuzzy points. This one is easy. What Nginx does in
case client stalls and proxied server still sends data? HTTP protocol has no
flow control either.
Posted at Nginx Forum: http://forum.nginx.org/read.php?2,237158,241050#msg-241050