I am upgrading the haproxy from 2.4.2 to 3.0.9 in a project, in which haproxy is used to route HTTP2 message. There is a global configuration “timeout http-request 10s” in the configuration file. After the upgrade, I find that after a client connects to the haproxy server to send a HTTP2 request message, if there is no more message exchange in 10 seconds, haproxy as server side will send HTTP2 GOAWAY message to the client to end this session. But there is no such problem in version 2.4.2. After I change this configuration to 30 seconds, then the session may be kept 30 seconds in the similar scenario. But as the reference of haproxy document, this configuraion is used to “Set the maximum allowed time to wait for a complete HTTP request”, why does it impact the session duration? Could anybody provide a clue for it? Or is it a bug?
2 posts - 2 participants