Hello Joseph,
On Sun, 2 Sep 2018 at 03:42, Joseph Sible <[email protected]> wrote: > > When using HTTP/2, is there a way to force haproxy to send a GOAWAY > frame after a given response? I expected that "option forceclose" > might do this, but I tested it and it doesn't seem to. My use-case for > this is having a way to force re-establishment of the TLS connection, I think this should be done with a 421 Misdirect instead of a GOAWAY: https://tools.ietf.org/html/rfc7540#section-9.1.2 The 421 is there to make sure the browser sends the same request again on a different connection. GOAWAY is different in that regard and depending on what the last frame id in the GOAWAY header is, a browser may or may not retry the request. You might be able to do with a dedicated backend and a 503 errorfile. backend generate_421 errorfile 503 /etc/haproxy/421misdirect.http With appropriate content in /etc/haproxy/421misdirect.http Would you mind elaborating why you want to close the TLS connection, for a better understanding of the use-case? Regards, Lukas
