Hello. I came to understand why 200 is stored in the $status variable when proxy_read_timeout occurs. Thank you for the reply. 2024년 1월 17일 (수) 오전 7:27, Maxim Dounin <mdounin@mdounin.ru>님이 작성: > Hello! > > On Tue, Jan 16, 2024 at 01:15:09PM +0900, 박규철 wrote: > > > This is a question about the "$status" log value when > "proxyby park - Nginx Mailing List - English
Hello. This is a question about the "$status" log value when "proxy_read_timeout" occurs. Nginx version in use: v1.25.3 Contents of 1Mbyte size were requested to . A response up to approximately 500Kbytes in size, including the header, was received without delay. However, after 500Kbytes, no response was received from Origin for 3 seconds and the connection (time-out) Since tby park - Nginx Mailing List - English
Hello Thank you to everyone who answered. I came to understand that RFC 8673 is an experimental feature and is not in the feature support plan. Thank you for your answer again. 2022년 7월 12일 (화) 오후 7:31, Maxim Dounin <mdounin@mdounin.ru>님이 작성: > > Hello! > > On Tue, Jul 12, 2022 at 05:00:32PM +0900, 박규철 wrote: > > > I'm looking fby park - Nginx Mailing List - English
Hi. I'm looking for "low latency" related settings and functions to build faster services through Nginx. After many searches and functional tests, I thought that RFC 8673's behavior was necessary to implement "low latency". I have set up and tested the existing slice module, but I think it is insufficient to implement the "low latency" of RFC 8673. 1. I want to kby park - Nginx Mailing List - English