Re: Why set keepalive_timeout to a short period when Nginx is great at handling them?

Ah, I didn't know about NAT before. So that's how we have shared IP addresses vs. dedicated IP addresses. This is beautiful; there's so much to learn. So the 2^16 limitation that B.R. mentioned is nothing to worry about. It's like worrying that there are limited IP addresses available so we can't

Re: Why set keepalive_timeout to a short period when Nginx is great at handling them?

On Sunday 19 June 2016 16:06:56 Aahan Krish wrote: > Hi Valentin, > > *(I repeat the same question I put to B.R. as you raised the same > point.)* > > So you are referring to the 4-tuple (source_IP, source_port, > server_IP, server_port) socket limitation, correct? I just came to > know about

Re: Why set keepalive_timeout to a short period when Nginx is great at handling them?

Hi Valentin, *(I repeat the same question I put to B.R. as you raised the same point.)* So you are referring to the 4-tuple (source_IP, source_port, server_IP, server_port) socket limitation, correct? I just came to know about this and it's interesting. Please tell me if this understanding of

Re: Why set keepalive_timeout to a short period when Nginx is great at handling them?

On Saturday 18 June 2016 14:12:31 B.R. wrote: > There is no downside on the server application I suppose, especially since, > as you recalled, nginx got no trouble for it. > > One big problem is, there might be socket exhaustion on the TCP stack of > your front-end machine(s). Remember a socket

Re: Why set keepalive_timeout to a short period when Nginx is great at handling them?

Hi B.R., You raised a good point. So you are referring to the 4-tuple (source_IP, source_port, server_IP, server_port) socket limitation, correct? I just came to know about this and it's interesting. Please tell me if this understanding of mine is correct: So a server identifies a user's

Re: Why set keepalive_timeout to a short period when Nginx is great at handling them?

There is no downside on the server application I suppose, especially since, as you recalled, nginx got no trouble for it. One big problem is, there might be socket exhaustion on the TCP stack of your front-end machine(s). Remember a socket is defined by a triple and the

Why set keepalive_timeout to a short period when Nginx is great at handling them?

I read something interesting today: "Keep alive is a HTTP feature which allows user agents to keep the connection to your server open for a number of requests or until the specified time out is reached. This won’t