Hello!
On Fri, Nov 09, 2018 at 12:42:48PM -0500, nginxuser2018 wrote:
> We have tried different settings with 'lingering_close always;' and
> 'lingering_time', 'lingering_timeout' up to 240s with no success.
>
> Would you be able to confirm whether it is an nginx problem in the lingering
> close
Hi Maxim,
We have tried different settings with 'lingering_close always;' and
'lingering_time', 'lingering_timeout' up to 240s with no success.
Would you be able to confirm whether it is an nginx problem in the lingering
close automatic logic as you mentioned if I provide an example to reproduce
Hello!
On Mon, Nov 05, 2018 at 09:14:33AM -0500, nginxuser2018 wrote:
> I noticed that if I setup a simple scenario where a client is making
> concurrent requests on a server with nginx configured as a reverse proxy and
> SSL traffic termination endpoint, if I trigger a reload with 'nginx -s
> re
One setting that I noticed mitigates the problem is to use `lingering_close
always;` however in our infrastructure this can lead to the build up of
worker processes (for the duration of the lingering_timeout). What are the
advantages and drawbacks of using this setting?
Posted at Nginx Forum:
ht
I noticed that if I setup a simple scenario where a client is making
concurrent requests on a server with nginx configured as a reverse proxy and
SSL traffic termination endpoint, if I trigger a reload with 'nginx -s
reload' mid requests, often times the client will throw an
'javax.net.ssl.SSLExce
