diff options
| author | Maxim Dounin <mdounin@mdounin.ru> | 2023-02-02 23:38:48 +0300 |
|---|---|---|
| committer | Maxim Dounin <mdounin@mdounin.ru> | 2023-02-02 23:38:48 +0300 |
| commit | 2485681308bd8d3108da31546cb91bb97813a3fb (patch) | |
| tree | af077d3c55d14d356973707942b7bbb859c37f9c /auto | |
| parent | 384a8d8dfbf817b98715e8ed5ec7bf3cb545d501 (diff) | |
| download | nginx-2485681308bd8d3108da31546cb91bb97813a3fb.tar.gz nginx-2485681308bd8d3108da31546cb91bb97813a3fb.tar.bz2 | |
Lingering close for connections with pipelined requests.
This is expected to help with clients using pipelining with some constant
depth, such as apt[1][2].
When downloading many resources, apt uses pipelining with some constant
depth, a number of requests in flight. This essentially means that after
receiving a response it sends an additional request to the server, and
this can result in requests arriving to the server at any time. Further,
additional requests are sent one-by-one, and can be easily seen as such
(neither as pipelined, nor followed by pipelined requests).
The only safe approach to close such connections (for example, when
keepalive_requests is reached) is with lingering. To do so, now nginx
monitors if pipelining was used on the connection, and if it was, closes
the connection with lingering.
[1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=973861#10
[2] https://mailman.nginx.org/pipermail/nginx-devel/2023-January/ZA2SP5SJU55LHEBCJMFDB2AZVELRLTHI.html
Diffstat (limited to 'auto')
0 files changed, 0 insertions, 0 deletions