Hello, I was looking at maxconn behaviour on frontend side. I understood we don't trigger accept() once maxconn is reached https://git.haproxy.org/?p=haproxy.git;a=blob;f=src/listener.c;h=412af94a160662aa11802dd58512c6410c9b56da;hb=HEAD#l920 I wondered whether it would be an acceptable patch to add an option in order to accept() and close() the connection right after during such event. The context would be to "fail fast" on some environment where it is preferable to let know the client as soon as possible we can't accept the connection. In an environment where the haproxy instance is the second level of proxies, we want to fail fast instead of waiting for the end of tcp timeout to connect.
Thanks, -- William
