Hello Seth, unfortunately, this is incorrect.
HTTP/1.1 defines the "close" connection option for the sender to signal that the connection will be closed after completion of the response. https://tools.ietf.org/html/rfc2616#section-14.10 But the server with Ubuntus HAProxy 2.0.13 will not proactively do it. Therefore, as described above, it is very easy for a malicious application to fill up the servers memory and connection pool. With my minimal working example and a HAProxy docker container, you may easily and rather quickly be able to reproduce that. If this is expected behaviour, then I'm sorry for this ticket, which can be closed. (Migrated all my HAProxy based endpoints to a version not having this problem ;) ) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1919468 Title: HAProxy 2.0.13 does not close connection even though "connection: close" is sent, leaves many connections in CLOSE-WAIT state for HEAD- method requests To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/haproxy/+bug/1919468/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
