I kind of agree: keepalive connections are not strictly necessary in this
scenario.
But there is a reason why I started looking into this: I started noticing a lot
of closed tcp connections with status TIME_WAIT. That happens when you
close the connection on your end, and the os keeps these aroun
Hello!
On Mon, Dec 20, 2021 at 04:00:59PM +, Nicolas Franck wrote:
> Interesting!
>
> I looks like there is nothing that managing the incoming connections
> for the fcgi workers. Every fcgi worker needs to do this on its own, right?
> So if there are more clients (i.e. nginx workers) than fc
Interesting!
I looks like there is nothing that managing the incoming connections
for the fcgi workers. Every fcgi worker needs to do this on its own, right?
So if there are more clients (i.e. nginx workers) than fcgi workers,
then it becomes unresponsive after a few requests, because all
the fcgi
Hello!
On Sun, Dec 19, 2021 at 07:56:51PM +, Nicolas Franck wrote:
> In order to make nginx keep the tcp connections alive,
> I've added the following settings:
>
> * proxy_socket_keepalive on
> * proxy_http_version 1.1;
> * proxy_set_header Connection "";
Just a side note: you don't need a
I've created a server setup where nginx acts as
a proxy server for a fastcgi application.
That last application is running on a different server on port 9000.
It is spawn with spawn-fcgi.
Recently I have found out that nginx
closes the connection after every request.
In order to make nginx keep th
