Re: Force response to send HTTP/2 GOAWAY?

the browser to establish a new TLS connection so that it will use the client certificate that is now present. Joseph C. Sible

[RFC] Changing server port via Lua

uot;192.0.2.1 port ") Is this something that would be accepted if I wrote a patch for it? If so, which option should I go with for the Lua interface? [1]: https://stackoverflow.com/q/61568148/7509065 Joseph C. Sible

[PATCH] MINOR: lua: allow changing port with set_addr

Add an optional port parameter, which can be either a number or a string (to support '+' and '-' for port mapping). This fixes issue #586. --- doc/lua-api/index.rst | 2 +- src/hlua_fcn.c| 7 ++- 2 files changed, 7 insertions(+), 2 deletions(-) diff --git a/doc/lua-api/index.rst

Re: RFC: set minimum default TLS version to 1.2 for HAProxy 2.2

pecifying ssl-min-ver would previously have disallowed SSLv3, but will now allow it. (I hope this case doesn't actually exist anywhere in practice, but if it does for some reason, we probably don't want to make them even less secure.) Joseph C. Sible

Re: RFC: set minimum default TLS version to 1.2 for HAProxy 2.2

On Sat, May 30, 2020 at 3:22 PM William Lallemand wrote: > > On Sat, May 30, 2020 at 08:41:04PM +0200, William Lallemand wrote: > > On Sat, May 30, 2020 at 02:04:56PM -0400, Joseph C. Sible wrote: > > > > > > I'm happy about this change, but I notice a flaw in its

Re: RFC: set minimum default TLS version to 1.2 for HAProxy 2.2

On Sat, May 30, 2020 at 4:15 PM William Lallemand wrote: > > On Sat, May 30, 2020 at 03:41:51PM -0400, Joseph C. Sible wrote: > > Anyway, when max < TLSv1.2, I think we should make min default to max. > > I think this is what you mean by "fallback on min = max&q