Why Nginx Doesn't Implement FastCGI Multiplexing?
igor at sysoev.ru
Sat Jul 20 04:40:39 UTC 2013
On Jul 20, 2013, at 8:36 , momyc wrote:
>> The main issue with FastCGI connection multiplexing is lack of flow
> 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.
It closes both connections to a client and a backend, since HTTP lacks both
flow control and multiplexing.
More information about the nginx