Nicolas Duchon

I've pushed the following images: `nginxproxy/nginx-proxy:1642-1194` : nginx `1.19.4` `nginxproxy/nginx-proxy:1642-1195` : nginx `1.19.5` `nginxproxy/nginx-proxy:1642-1196` : nginx `1.19.6` `nginxproxy/nginx-proxy:1642-1197` : nginx `1.19.7` `nginxproxy/nginx-proxy:1642-1198` : nginx `1.19.8` `nginxproxy/nginx-proxy:1642-1199` : nginx `1.19.9` Could...

> Changes with nginx 1.19.7 16 Feb 2021 > > *) Change: connections handling in HTTP/2 has been changed to better > match HTTP/1.x; the "http2_recv_timeout", "http2_idle_timeout", and > "http2_max_requests"...

Additional info: We're not setting [`keepalive_timeout`](https://nginx.org/en/docs/http/ngx_http_core_module.html#keepalive_timeout) in the template so it has the default value of 75s. We're not setting [`auth_delay`](https://nginx.org/en/docs/http/ngx_http_core_module.html#auth_delay), [`limit_req`](https://nginx.org/en/docs/http/ngx_http_limit_req_module.html#limit_req), [`keepalive_requests`](https://nginx.org/en/docs/http/ngx_http_core_module.html#keepalive_requests) or [`keepalive_time`](https://nginx.org/en/docs/http/ngx_http_core_module.html#keepalive_time) either. We were not using...

https://trac.nginx.org/nginx/ticket/2155 > It turns out no browsers implement HTTP/2 GOAWAY handling properly, and > large enough number of resources on a page results in failures to load > some resources....

I figured from your screenshot that you're far from the ~1000 requests mentioned in the nginx issue, but it seems to be triggered even with a low requests count in...

@AndreasKappel which nginx keep alive variable specifically ?

What would be the possible implications of adding `keepalive_timeout 1` to the template for those who aren't affected by this issue ?

Hi. Could you elaborate on what this PR does and the security reasons that motivate those changes ? I'm not fluent enough in nginx to get it straight away.

@rhansen this PR would be superseded by #1927, right ?

@rhansen any preference on merging this PR first then #1927 or the inverse ?