Re: Problem: Port_443_lbb1/ - Error 400 BAD REQ

Hi. On 31.01.22 16:51, Roberto Carna wrote: Dear all, I have haproxy-1.5.18-3.el7.x86_64 running OK. You should consider to use a maintained version as 1.5 is End of Life from the community. https://www.haproxy.org/ https://github.com/DBezemer/rpm-haproxy Development area are claiming for a

Re: [PATCH] get BoringSSL back to the game

On Mon, Jan 31, 2022 at 10:22:01AM +0500, Илья Шипицин wrote: > > Hello, > Hello Ilya, > 0001 .. 0003 are "pre QUIC" patches > 0004 .. 0006 are most questionable QUIC part > 0007 is very simple > > > we can discuss whether BoringSSL should be > 1) dropped completely > 2) supporte

Re: [PATCH] get BoringSSL back to the game

вт, 1 февр. 2022 г. в 15:35, William Lallemand : > On Mon, Jan 31, 2022 at 10:22:01AM +0500, Илья Шипицин wrote: > > > > Hello, > > > > Hello Ilya, > > > 0001 .. 0003 are "pre QUIC" patches > > 0004 .. 0006 are most questionable QUIC part > > 0007 is very simple > > > > > > we can d

DOC issue with http-request return

I think I've found an error in the docs. The entry for `http-request return` shows the last component as [ {if | unless} ] but if I leave that off in a backend I get [ALERT] parsing... 'http-request return' expects either 'if' or 'unless' followed by a condition but found ‘…'. I’ve attached a

[ANNOUNCE] haproxy-2.6-dev1

Hi, HAProxy 2.6-dev1 was released on 2022/02/01. It added 379 new commits after version 2.6-dev0. That first development release is huge (379 commits), essentially because by being busy on bugs we didn't see the time fly and forgot to emit earlier versions as I wanted to. Too bad. Now the punishm

Re: [ANNOUNCE] haproxy-2.6-dev1

On Tue, Feb 01, 2022 at 07:41:08PM +0100, Willy Tarreau wrote: > - master-worker: some simplifications were applied to the way the new > process connects to the old one to retrieve listening sockets. In the > past it would rely on "-x" on the command line, or would try to connect > to

Re: Per-client queue for rate limiting?

--- Original Message --- On Sunday, January 30th, 2022 at 2:18 AM, Orlando Della Casa wrote: > I’d like to put a rate limit on incoming HTTP requests, but without sending > 429 errors. You could simply delay the request with Lua. We use a stick table to track requests and if an IP ex

[PATCH] CI: enable QUIC for Coverity scan

Hello, since QUIC is first class citizen, let us scan it in code analysis. Ilya From dd316a69698299f0bfc5ec7a86133f83dc1061a3 Mon Sep 17 00:00:00 2001 From: Ilya Shipitsin Date: Wed, 2 Feb 2022 10:24:58 +0500 Subject: [PATCH] CI: enable QUIC for Coverity scan --- .github/workflows/coverity.ym