On Wed, Apr 03, 2013 at 06:01:31PM +0200, Lukas Tribus wrote:
> Thank you, you did an amazing job here again!
Thanks! You know, people like you who qualify bug reports on the
ML help save a lot of time and shorten the time to produce a fix.
> > TLS ALPN was implemented similarly as NPN was made.
Thank you, you did an amazing job here again!
> TLS ALPN was implemented similarly as NPN was made. It is supposed
> to replace NPN.
Jesus Christ, this was fast. It was only discussed at IETF 86 mid-march
(and in 2 drafts this year), and 15 days later its already in
haproxy-1.5.
I think HAProxy
Hi,
here's an update for 1.5. It contains a security fix, please read, as
you'll want either to update or to apply the fix on top of your version
if you are running it.
Configurations at risk are those which combine use of HTTP keywords in
TCP content inspection rules, client-side keep-alive, hea
3 matches
Mail list logo