[ANNOUNCE] haproxy-3.1-dev8

Hi, HAProxy 3.1-dev8 was released on 2024/09/18. It added 50 new commits after version 3.1-dev7. The last two weeks have been mostly dedicated to fixing bugs in order to update stable branches, so it will be no surprise that this version mostly contains fixes as well. They are not even

Re: haproxy-3.x.x - Ubuntu Focal

On 2024-09-11 08:40, Alexis Vachette wrote: Just wanted to know if you had a plan to release package for Ubuntu 20.04 Focal. Mostly because of OpenSSL 3.0 regression performance. The question is more for Vincent Bernat. I've just pushed a build for Ubuntu Focal.

Re: haproxy-3.x.x - Ubuntu Focal

e to install a package of an older distro on a newer one, but that could be convenient. Otherwise if you only want packaged stuff for Ubuntu 20, Vincent still provides haproxy up to 2.9 (that includes 2.8 which is LTS). But at some point you might have to build packages yourself if you need an extende

Re: haproxy-3.x.x - Ubuntu Focal

ср, 11 сент. 2024 г. в 08:44, Alexis Vachette : > Hi, > > Just wanted to know if you had a plan to release package for Ubuntu 20.04 > Focal. > > Mostly because of OpenSSL 3.0 regression performance. > > The question is more for Vincent Bernat. > I wonder what are your expectation of SSL lib for t

haproxy-3.x.x - Ubuntu Focal

Hi, Just wanted to know if you had a plan to release package for Ubuntu 20.04 Focal. Mostly because of OpenSSL 3.0 regression performance. The question is more for Vincent Bernat. Regards, -- *Alexis Vachette*Expert Network Engineer

[ANNOUNCE] haproxy-3.1-dev7

Hi, HAProxy 3.1-dev7 was released on 2024/09/05. It added 56 new commits after version 3.1-dev6. This version collects a non-negligible number of bug fixes (16) including the important one affecting H2+zero-copy forwarding mentioned in the 3.0 and 2.9 announcements. The other bugs that were

Re: [ANNOUNCE] haproxy-3.0.4

Hi, On Tue, Sep 03, 2024 at 03:52:43PM +0200, Willy Tarreau wrote: > HAProxy 3.0.4 was released on 2024/09/03. It added 42 new commits > after version 3.0.3. (...) > Note that at this point this flushes the queue of pending bugs for 3.0, > which is a good news. There remains one

[ANNOUNCE] haproxy-2.9.10

Hi, HAProxy 2.9.10 was released on 2024/09/03. It added 52 new commits after version 2.9.9. This release groups all backportable fixes shipped in the 3.0.3 and 3.0.4. The main topic is about fixes of two issues affecting how the H2 mux deals with incomplete frames: - in one case, certain

[ANNOUNCE] haproxy-3.0.4

Hi, HAProxy 3.0.4 was released on 2024/09/03. It added 42 new commits after version 3.0.3. This version addresses two issues affecting how the H2 mux deals with incomplete frames: - in one case, certain errors happening while processing an incomplete frame did not lead to the termination

Re: [PATCH] CLEANUP: haproxy: fix typos in code comment

Hi Nicolas, On Tue, Aug 27, 2024 at 10:18:51PM +0200, Nicolas CARPi wrote: > Found these two typos while browsing the code :) (...) > Found this typo in macro name :) Thank you, both patches applied. > BTW, in mqtt.c mqtt_read_varint(), "off" is initialized to 0, but > initialized again in the

[PATCH] CLEANUP: haproxy: fix typos in code comment

Hello, Found these two typos while browsing the code :) Wanted to see how haproxy gets random bytes. That seed initialization code really goes out of its way to grab all entropy it can find! ^^ Best, ~Nico >From b71acb32c4122819d50dac11ae60bb5cac1faba8 Mon Sep 17 00:00:00 2001 From: Nico

Re: HAProxy returning 502 with SH--

> but is still close enough that it may be worth a try: > > https://github.com/haproxy/haproxy/issues/2665 > > > > Lukas >

Re: HAProxy returning 502 with SH--

Also, before doing anything else, try using: tune.disable-zero-copy-forwarding or tune.h1.zero-copy-fwd-recv off as there is currently an open bug that doesn't fully match your case but is still close enough that it may be worth a try: https://github.com/haproxy/haproxy/issues/2665 Lukas

Re: HAProxy returning 502 with SH--

Hello, On Tue, 27 Aug 2024 at 18:09, BJ Taylor wrote: > > Here are the 502 logs from the last run after the config changes. > > 2024-08-26T09:29:02.547581-06:00 testserver haproxy[284569]: <134>Aug 26 > 09:29:02 haproxy[284569]: 192.168.69.101:45382 [26/Aug/2024:09:29:0

Re: HAProxy returning 502 with SH--

Here are the 502 logs from the last run after the config changes. 2024-08-26T09:29:02.547581-06:00 testserver haproxy[284569]: <134>Aug 26 09:29:02 haproxy[284569]: 192.168.69.101:45382 [26/Aug/2024:09:29:02.545] www~ front3/pdafront32 0/0/0/-1/1 502 208 - - SH-- 5/5/3/3/0 0/0 { front3.doma

[PATCH v2 0/4] Add MPTCP to haproxy

) - Separated the changes to str2sa_range into a different patch (https://www.mail-archive.com/haproxy@formilux.org/msg45229.html). This function adds a new "alt" parameter that can be used to get an alternate protocol to use. (Willy) - Patch 2: (new) - Add

Re: HAProxy returning 502 with SH--

I will make the suggested changes and try again. Here are the failure logs for the last run. Queues are 0, current connections are not all that high. Aug 22 01:12:12 haproxy[87118]: > {"host":"testserver","ident":"haproxy","pid":8711

Re: HAProxy returning 502 with SH--

On Fri, 23 Aug 2024 at 18:55, BJ Taylor wrote: > > We are trying to deploy HAProxy into our environment. We have a script that > does some 600k api calls during approximately 24 hours. How many concurrent connections / transactions though? > During that time, when haproxy is in

HAProxy returning 502 with SH--

We are trying to deploy HAProxy into our environment. We have a script that does some 600k api calls during approximately 24 hours. During that time, when haproxy is in place, there are a handful (8-12) of responses that come back as 502 with SH--. We've tested this against Ubuntu's d

Re: [PATCH 0/2] Add MPTCP to haproxy

On 23/08/2024 17:20, Willy Tarreau wrote: > On Fri, Aug 23, 2024 at 05:11:11PM +0200, Matthieu Baerts wrote: (...) >> Maybe a new socket option would be better if the idea is only to >> silently drop connections? :) > > Yes, probably. Right now it's done directly in the action itself > (tcp_exec

Re: [PATCH 0/2] Add MPTCP to haproxy

R, > > which was initially defined for CRIU, and that we're using to silently > > destroy a connection without responding. It's extremely effective against > > HTTP botnets as they keep their connection pending and do not consume > > anything locally. I don't

Re: [PATCH 0/2] Add MPTCP to haproxy

; which was initially defined for CRIU, and that we're using to silently > destroy a connection without responding. It's extremely effective against > HTTP botnets as they keep their connection pending and do not consume > anything locally. I don't know if you have it, but if

Re: [PATCH 0/2] Add MPTCP to haproxy

REPAIR, which was initially defined for CRIU, and that we're using to silently destroy a connection without responding. It's extremely effective against HTTP botnets as they keep their connection pending and do not consume anything locally. I don't know if you have it, but if you're interested in giving it a try, I can help you set it up in haproxy for a test. Cheers, Willy

Re: [PATCH 0/2] Add MPTCP to haproxy

as long as TCP_MAXSEG is not supported). For the moment, >> MPTCP doesn't support TCP_MAXSEG socket option, mainly because it >> has apparently never been requested before, apparently. It should >> not be difficult to implement it, but is it an important option &g

Re: [PATCH 0/2] Add MPTCP to haproxy

t support TCP_MAXSEG socket option, mainly because it > has apparently never been requested before, apparently. It should > not be difficult to implement it, but is it an important option > for HAProxy? It's not that common anymore but 15 years ago when ADSL over PPPoE was

[PATCH 0/2] Add MPTCP to haproxy

efore, apparently. It should not be difficult to implement it, but is it an important option for HAProxy? Link: https://www.rfc-editor.org/rfc/rfc8684.html [1] Link: https://www.tessares.net/apples-mptcp-story-so-far/ [2] Link: https://www.mptcp.dev [3] Link: https://www.mail-archive.com/ha

[ANNOUNCE] haproxy-3.1-dev6

Hi, HAProxy 3.1-dev6 was released on 2024/08/21. It added 67 new commits after version 3.1-dev5. A few minor bugs were fixed, with the most important one probably be the recent breakage of command pipeling on the master CLI (commands delimited by semi-colons passed to a worker). Aside this, the

Re: [ANNOUNCE] haproxy-3.1-dev5

Hi Ilya, On Wed, Aug 07, 2024 at 08:30:46PM +0200, ??? wrote: > > HAProxy 3.1-dev5 was released on 2024/08/07. It added 88 new commits > > after version 3.1-dev4. > > > > There were quite a bunch of fixes this time, spread over various areas > > (h2, analy

Re: [ANNOUNCE] haproxy-3.1-dev5

ср, 7 авг. 2024 г. в 18:48, Willy Tarreau : > Hi, > > HAProxy 3.1-dev5 was released on 2024/08/07. It added 88 new commits > after version 3.1-dev4. > > There were quite a bunch of fixes this time, spread over various areas > (h2, analysers, jwt, quic, 0-rtt, queues, tr

[ANNOUNCE] haproxy-3.1-dev5

Hi, HAProxy 3.1-dev5 was released on 2024/08/07. It added 88 new commits after version 3.1-dev4. There were quite a bunch of fixes this time, spread over various areas (h2, analysers, jwt, quic, 0-rtt, queues, traces), though nothing exciting at this point. We've got a report of a user f

Re: [ANNOUNCE] haproxy-3.0.3

On Sun, Aug 04, 2024 at 09:39:25PM +0200, Vincent Bernat wrote: > > On 2024-07-22 21:59, Willy Tarreau wrote: > > > > > HAProxy 3.0.3 was released on 2024/07/11. It added 42 new commits > > > > after version 3.0.2. > > > > > > I am late r

Re: [ANNOUNCE] haproxy-3.0.3

On 2024-07-22 21:59, Willy Tarreau wrote: HAProxy 3.0.3 was released on 2024/07/11. It added 42 new commits after version 3.0.2. I am late releasing this version on haproxy.debian.net. I have issues with compiling for ARM64. There is a known bug in recent version of QEMU segfaulting on

Re: Some HTTP connections not closing properly on Haproxy 2.8.10

Hi, I finally found some issues. Not sure it is exactly yours. But it is very similar. So I'm confident. I pushed 3 new fixes in 3.1-DEV. It may be good to check on the 3.0 if this fully fixes all your issues. And eventually, if possible, on 2.8 too, with the splicing enabled. In attachement

Re: Some HTTP connections not closing properly on Haproxy 2.8.10

Le 30/07/2024 à 17:23, Jens Wahnes a écrit : Thanks for the confirmation. On 3.0, I was unable to reproduce the issue. So I'm not surprised. On version 3.0.3 with splicing turned on, I actually did end up with a backend connection in state CLOSE_WAIT that is still around after some hours. But i

Re: Some HTTP connections not closing properly on Haproxy 2.8.10

on the 2.8 and figure out if upper versions are affected too. I'm able to reproduce the issue by hacking the code, forcing a connection error by hand. It occurs when an error is reported on the connection when haproxy tries to send data using kernel splicing. But it is only an issue when a f

Re: Some HTTP connections not closing properly on Haproxy 2.8.10

are affected too. I'm able to reproduce the issue by hacking the code, forcing a connection error by hand. It occurs when an error is reported on the connection when haproxy tries to send data using kernel splicing. But it is only an issue when a filter is attached to the applicative stre

Re: Some HTTP connections not closing properly on Haproxy 2.8.10

e the issue by hacking the code, forcing a connection error by hand. It occurs when an error is reported on the connection when haproxy tries to send data using kernel splicing. But it is only an issue when a filter is attached to the applicative stream. I guess you have enabled the HTTP compre

Re: Some HTTP connections not closing properly on Haproxy 2.8.10

code, forcing a connection error by hand. It occurs when an error is reported on the connection when haproxy tries to send data using kernel splicing. But it is only an issue when a filter is attached to the applicative stream. I guess you have enabled the HTTP compression. The response i

Re: Some HTTP connections not closing properly on Haproxy 2.8.10

Le 26/07/2024 à 19:51, Jens Wahnes a écrit : Hi everyone, I'm trying to move from Haproxy 2.4 to 2.8 and encountered some trouble with 2.8 that did not occur on 2.4. Specifically, this seems to concern plain HTTP connections only, i.e. non-HTTPS traffic. I have not seen an example of

Re: Some HTTP connections not closing properly on Haproxy 2.8.10

f the backend connections are not properly closed with Haproxy 2.8 and keep lingering for hours or days. That is, the client connection is gone, but the backend connection is still there in state CLOSE_WAIT. This in turn causes trouble with seamless reloads: the old Haproxy processes never terminate a

Re: Some HTTP connections not closing properly on Haproxy 2.8.10

Hi Jens, On Fri, Jul 26, 2024 at 07:51:47PM +0200, Jens Wahnes wrote: > Hi everyone, > > I'm trying to move from Haproxy 2.4 to 2.8 and encountered some trouble with > 2.8 that did not occur on 2.4. > Specifically, this seems to concern plain HTTP connections only, i.e. &g

Some HTTP connections not closing properly on Haproxy 2.8.10

Hi everyone, I'm trying to move from Haproxy 2.4 to 2.8 and encountered some trouble with 2.8 that did not occur on 2.4. Specifically, this seems to concern plain HTTP connections only, i.e. non-HTTPS traffic. I have not seen an example of this happening with HTTPS connections. Howeve

Re: [ANNOUNCE] haproxy-3.1-dev2

On 2024-07-26 (Fr.) 10:49, Willy Tarreau wrote: On Fri, Jul 26, 2024 at 10:40:46AM +0200, ??? wrote: next point: 0-RTT Sorry for the stupid questions but as I don't maintain any QUIC based apps I'm curious if this really makes any differences compared to "normal" requests. How oft

Re: [ANNOUNCE] haproxy-3.1-dev2

On Fri, Jul 26, 2024 at 10:40:46AM +0200, ??? wrote: > > > next point: 0-RTT > > > > Sorry for the stupid questions but as I don't maintain any QUIC based apps > > I'm > > curious if this really makes any differences compared to "normal" requests. > > > > How often is this really used in t

Re: [ANNOUNCE] haproxy-3.1-dev2

not implemented by AWS-LC, > and is > > disabled by default in a lot of stack anyway. > > > > > > next point: 0-RTT > > Sorry for the stupid questions but as I don't maintain any QUIC based apps > I'm > curious if this really makes any diff

Re: [ANNOUNCE] haproxy-3.1-dev2

any differences compared to "normal" requests. How often is this really used in the real world setup? Have anybody seen any real benefit for users out there with 0-RTT? according to haproxy/include/haproxy/openssl-compat.h at master · haproxy/haproxy (github.com) <https://gith

Re: [ANNOUNCE] haproxy-3.1-dev2

пт, 26 июл. 2024 г. в 09:14, William Lallemand : > On Thu, Jul 25, 2024 at 11:22:25PM +0200, Илья Шипицин wrote: > > Subject: Re: [ANNOUNCE] haproxy-3.1-dev2 > > чт, 25 июл. 2024 г. в 22:00, Илья Шипицин : > > > > > > > > > > > чт, 25 июл. 2024 г.

Re: [ANNOUNCE] haproxy-3.1-dev2

On Thu, Jul 25, 2024 at 11:22:25PM +0200, Илья Шипицин wrote: > Subject: Re: [ANNOUNCE] haproxy-3.1-dev2 > чт, 25 июл. 2024 г. в 22:00, Илья Шипицин : > > > > > > > чт, 25 июл. 2024 г. в 14:27, William Lallemand : > > > >> On Wed, Jul 03, 2024 at

Re: [ANNOUNCE] haproxy-3.1-dev2

0_POLY1305 for >> QUIC with AWS-LC. >> > > nice, it passes chacha20 test! > > >> We now handle with AWS-LC for QUIC: >> - TLS_AES_128_GCM_SHA256 >> - TLS_AES_256_GCM_SHA384 >> - TLS_CHACHA20_POLY1305_SHA256 >> >> The TLS_AES_128_CCM_SHA256 cipher

Re: [ANNOUNCE] haproxy-3.1-dev2

чт, 25 июл. 2024 г. в 14:27, William Lallemand : > On Wed, Jul 03, 2024 at 11:51:21PM +0200, William Lallemand wrote: > > > aws-lc implements chacha20_poly1305 in a different way than QuicTLS. > > > and if that gap is eliminated, it will be a good point to declare > aws-lc as > > > a recommended Q

Re: [ANNOUNCE] haproxy-3.1-dev4

On Wed, 24 Jul 2024 at 23:19, William Lallemand wrote: > > On Wed, Jul 24, 2024 at 10:32:16PM +0200, Aleksandar Lazic wrote: > > Does this announcement have any impact to HAProxy? > > > > "Intent to End OCSP Service" > > https://letsencrypt.org/2024/07/23

Re: [ANNOUNCE] haproxy-3.1-dev2

On Wed, Jul 03, 2024 at 11:51:21PM +0200, William Lallemand wrote: > > aws-lc implements chacha20_poly1305 in a different way than QuicTLS. > > and if that gap is eliminated, it will be a good point to declare aws-lc as > > a recommended QUIC lib. > > > > if we compare aws-lc against openssl-1.1 (

Re: [ANNOUNCE] haproxy-3.1-dev4

ср, 24 июл. 2024 г. в 23:22, William Lallemand : > > On Wed, Jul 24, 2024 at 10:32:16PM +0200, Aleksandar Lazic wrote: > > Does this announcement have any impact to HAProxy? > > > > "Intent to End OCSP Service" > > https://letsencrypt.org/2024/07/23

Re: [ANNOUNCE] haproxy-3.1-dev4

On Wed, Jul 24, 2024 at 10:32:16PM +0200, Aleksandar Lazic wrote: > Does this announcement have any impact to HAProxy? > > "Intent to End OCSP Service" > https://letsencrypt.org/2024/07/23/replacing-ocsp-with-crls.html > https://news.ycombinator.com/item?id=41046

Re: [ANNOUNCE] haproxy-3.1-dev4

handle this topic, even I don't use it for now :-) > > Hehe, who knows, maybe one day you'll have a good use for it :-) > > > >- ocsp: some processing was refined to better handle a corner case > > > where > > > the issuer chain is not in the sa

Re: [ANNOUNCE] haproxy-3.1-dev4

>- ocsp: some processing was refined to better handle a corner case where > > the issuer chain is not in the same PEM file, though it also slightly > > changes how this is handled on the CLI. > > [snipp] > > Does this announcement have any impact to HAProxy? >

Re: [ANNOUNCE] haproxy-3.1-dev4

On 2024-07-24 (Mi.) 18:50, Willy Tarreau wrote: Hi, HAProxy 3.1-dev4 was released on 2024/07/24. It added 113 new commits after version 3.1-dev3. Some nice goodies came in this version: [snipp] - SPOE: the old applet-based architecture was replaced with the new mux-based one

[ANNOUNCE] haproxy-3.1-dev4

Hi, HAProxy 3.1-dev4 was released on 2024/07/24. It added 113 new commits after version 3.1-dev3. Some nice goodies came in this version: - QUIC now has support for sending frames using GSO, which can save quite some significant CPU cycles since a single syscall will be used for

Re: [ANNOUNCE] haproxy-3.0.3

Hi Vincent, On Mon, Jul 22, 2024 at 09:25:45PM +0200, Vincent Bernat wrote: > On 2024-07-11 16:51, Willy Tarreau wrote: > > Hi, > > > > HAProxy 3.0.3 was released on 2024/07/11. It added 42 new commits > > after version 3.0.2. > > I am late releasing this vers

Re: [ANNOUNCE] haproxy-3.0.3

On 2024-07-11 16:51, Willy Tarreau wrote: Hi, HAProxy 3.0.3 was released on 2024/07/11. It added 42 new commits after version 3.0.2. I am late releasing this version on haproxy.debian.net. I have issues with compiling for ARM64. There is a known bug in recent version of QEMU segfaulting on

Re: [ANNOUNCE] haproxy-3.1-dev3 (more infos on the story with fd-hard-limit and systemd)

On Wed, Jul 17, 2024 at 02:06:03PM +0200, Lukas Tribus wrote: > On Wed, 17 Jul 2024 at 11:25, Willy Tarreau wrote: > > > > At this point, do you (or anyone else) still have any objection against > > backporting the DEFAULT_MAXFD patch so as to preserve the current > > defaults for users, and/or do

Re: [ANNOUNCE] haproxy-3.1-dev3 (more infos on the story with fd-hard-limit and systemd)

On Wed, 17 Jul 2024 at 11:25, Willy Tarreau wrote: > > At this point, do you (or anyone else) still have any objection against > backporting the DEFAULT_MAXFD patch so as to preserve the current > defaults for users, and/or do you have any alternate proposal, or just > want to discuss other possib

Re: [ANNOUNCE] haproxy-3.1-dev3 (more infos on the story with fd-hard-limit and systemd)

t > 1GB of memory for 20k non-TLS connections or 8k TLS connections, but > my test was indeed synthetic with zero features used, and it's not > only about haproxy userspace but the system as well. Yes, it's really a whole. Its even more difficult nowadays because it depends

Re: [ANNOUNCE] haproxy-3.1-dev3 (more infos on the story with fd-hard-limit and systemd)

for 20k non-TLS connections or 8k TLS connections, but my test was indeed synthetic with zero features used, and it's not only about haproxy userspace but the system as well. lukas@dev:~/haproxy$ git grep -B3 -A1 "GB of RAM" doc/configuration.txt- global maxconn. Also, keep

Re: [ANNOUNCE] haproxy-3.1-dev3 (more infos on the story with fd-hard-limit and systemd)

ll details here: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1074374 It's on DebianTrixie, amd64 Our issue in GITHUB: https://github.com/haproxy/haproxy/issues/2621 You agree that this is the environment systemd sets us up with, right? Yes, as it was investigated by Apollon system

Re: [PATCH 1/1]: BUILD/MINOR: haproxy: fix SO_LINGER usage on macOs.

On Tue, Jul 16, 2024 at 05:27:10AM +0100, David CARLIER wrote: > Hi you are right I did not check properly, had a brain fog :) we can forget > it. Thanks. OK perfect, thanks :-) Willy

Re: [PATCH 1/1]: BUILD/MINOR: haproxy: fix SO_LINGER usage on macOs.

> > > > Cheers. > > > From df5741a0d391a7107157d0051ba81ef48d87b8f5 Mon Sep 17 00:00:00 2001 > > From: David Carlier > > Date: Mon, 15 Jul 2024 22:20:33 +0100 > > Subject: [PATCH] BUILD/MEDIUM: haproxy : fix SO_LINGER usage on macOS. > > > > S

Re: [PATCH 1/1]: BUILD/MINOR: haproxy: fix SO_LINGER usage on macOs.

> Subject: [PATCH] BUILD/MEDIUM: haproxy : fix SO_LINGER usage on macOS. > > SO_LINGER on macOS works in term of clock ticks rather than seconds > leading to behavior differences. SO_LINGER_SEC is available to > be more in line so we create HA_SO_LINGER internal. How would that mak

[PATCH 1/1]: BUILD/MINOR: haproxy: fix SO_LINGER usage on macOs.

Hi here a little patch proposal targeted for macOs. Cheers. 0001-BUILD-MEDIUM-haproxy-fix-SO_LINGER-usage-on-macOS.patch Description: Binary data

[ANNOUNCE] haproxy-3.0.3

Hi, HAProxy 3.0.3 was released on 2024/07/11. It added 42 new commits after version 3.0.2. This version closes the list of pending issues for 3.0. Fixed in this release are: - a QUIC bug affecting 3.0 and above only, by which can trigger a BUG_ON (hence a crash) sometimes when trying to

Re: [ANNOUNCE] haproxy-3.1-dev3

hat is offered but only a smaller subset that matches what was commonly encountered till now. So if we start with 1B fd regardless of the amount of RAM, we want to limit to a lower value so as not to OOM for no reason. One FD takes 64 bytes. Starting haproxy with 1M FDs here takes ~80 MB, whic

Re: [ANNOUNCE] haproxy-3.1-dev3

Hi, I will get back to this for further research and discussion in about a week. In the meantime, do we agree that the environment we are developing the fix for is the following: the hard limit is always set to the maximum available in the kernel which on amd64 is one billion with a B, whether t

Re: [ANNOUNCE] haproxy-3.1-dev3

will need to be backported after some time concerns > > the handling of default FD limits. (...) > I wholeheartedly hate default implicit limits and I also pretty much > disagree with fd-hard-limit in general, but allow me to quote your own > post here from github issue #2043 comment > h

Re: [ANNOUNCE] haproxy-3.1-dev3

bug report will be that haproxy OOM's (in production and only when encountering load) by default with systems with less than 16 GB of RAM. The same bug reporter just needs a VM with 8 GB RAM or less. Sometimes the hard choices need to be up to the user. I believe this is some of those times. cheers lukas

Re: [ANNOUNCE] haproxy-3.1-dev3

(which in itself is not > necessarily a bad thing -- proof that I'm not always bashing systemd, only > when needed :-)). But with some machines showing extreme nr_open (I still > don't know why) we're back to square one where it's possible for haproxy > to try to

Re: [ANNOUNCE] haproxy-3.1-dev3

On Wed, Jul 10, 2024 at 06:49:52PM +0200, Aleksandar Lazic wrote: > > > On 2024-07-10 (Mi.) 16:39, Willy Tarreau wrote: > > Hi, > > > > HAProxy 3.1-dev3 was released on 2024/07/10. It added 35 new commits > > after version 3.1-dev2. > > [snipp] > >

Re: [ANNOUNCE] haproxy-3.1-dev3

On 2024-07-10 (Mi.) 16:39, Willy Tarreau wrote: Hi, HAProxy 3.1-dev3 was released on 2024/07/10. It added 35 new commits after version 3.1-dev2. [snipp] And I'm still trying to free some time for the pending reviews (I have not forgotten you but stuff that depends on multiple pe

[ANNOUNCE] haproxy-3.1-dev3

Hi, HAProxy 3.1-dev3 was released on 2024/07/10. It added 35 new commits after version 3.1-dev2. This version mostly addresses some issues affecting dev2, a few of which could cause crashes. Some of them are marked for backporting because they also affect older versions (races between server

【三井住友カード】不正利用からアカウントを保護するために追加情報が必要haproxy

三井住友カード会員　様 いつも三井住友カードをご利用頂きありがとうございます。 カードがご利用いただけなかったお取引がございましたのでお知らせいたします。 ◇利用カード：三井住友カード ◇利用日：2024/07/04 5:04:33 ◇利用先：ＴＯＹＯＴＡＷａｌｌｅｔチャージ ◇利用金額：50,000円 不正利用検知システムで第三者による不正の可能性を検知したため、上記取引を制限させていただきました。 以下の回答ページよりご利用内容の確認にご協力ください。 ▼回答ページはこちら（所要時間：30秒） 3024.szsmxf.com/5205 URLをコピーしてWebブラウザー

Re: [ANNOUNCE] haproxy-3.1-dev2

On Wed, Jul 03, 2024 at 11:18:12PM +0200, Илья Шипицин wrote: > Subject: Re: [ANNOUNCE] haproxy-3.1-dev2 > сб, 29 июн. 2024 г. в 12:01, Willy Tarreau : > > > Hi, > > > > HAProxy 3.1-dev2 was released on 2024/06/29. It added 45 new commits > > after version 3.1-de

Re: [ANNOUNCE] haproxy-3.1-dev2

сб, 29 июн. 2024 г. в 12:01, Willy Tarreau : > Hi, > > HAProxy 3.1-dev2 was released on 2024/06/29. It added 45 new commits > after version 3.1-dev1. > > Several fixes related to the recent 3.0 release are present in this > version, as well as a few older ones. Most v

[ANNOUNCE] haproxy-3.1-dev2

Hi, HAProxy 3.1-dev2 was released on 2024/06/29. It added 45 new commits after version 3.1-dev1. Several fixes related to the recent 3.0 release are present in this version, as well as a few older ones. Most visible are three QUIC crashes, a possible double free on stick-tables, issues affecting

[ANNOUNCE] haproxy-2.4.27

Hi, HAProxy 2.4.27 was released on 2024/06/18. It added 43 new commits after version 2.4.26. This version follows the first release of 3.0. Here is a summary of the most notable changes. One fix was applied for better HTTP error reporting. In some cases, 502 server initial errors were

[ANNOUNCE] haproxy-2.6.18

Hi, HAProxy 2.6.18 was released on 2024/06/18. It added 82 new commits after version 2.6.17. This version follows the first release of 3.0. Here is a summary of the most notable changes. Several fixes are applied for better HTTP conformance. In some cases, 502 server initial errors were

Re: HAProxy 3.0 for Debian Bullseye?

Hi On 6/16/24 14:39, Vincent Bernat wrote: Yes, that's possible. I didn't want to do that unless there is at least one user. I'll do it later today. Thank you, greatly appreciated. Best regards Tim Düsterhus

Re: HAProxy 3.0 for Debian Bullseye?

On 2024-06-16 14:37, Tim Düsterhus wrote: Hi Vincent, On 5/29/24 17:07, Willy Tarreau wrote: HAProxy 3.0.0 was released on 2024/05/29. It added 21 new commits after version 3.0-dev13. I do appreciate that everything was only cosmetic. I'm seeing that HAProxy 3.0 is already availab

HAProxy 3.0 for Debian Bullseye? (was: [ANNOUNCE] haproxy-3.0.0)

Hi Vincent, On 5/29/24 17:07, Willy Tarreau wrote: HAProxy 3.0.0 was released on 2024/05/29. It added 21 new commits after version 3.0-dev13. I do appreciate that everything was only cosmetic. I'm seeing that HAProxy 3.0 is already available on haproxy.debian.net since some

Re: [ANNOUNCE] haproxy-3.0.0

Hi On 5/29/24 21:37, Willy Tarreau wrote: - The version table on haproxy.org still has the EOL column for 2.0 in bold. Other EOL versions are not bold, so that's inconsistent. Ah, that makes sense, you're right. Now fixed! I'm just noticing a few more things: - For 3.0 the "Release date" ha

Re: [ANNOUNCE] haproxy-3.1-dev1

Le 14/06/2024 à 16:22, Christopher Faulet a écrit : Le 14/06/2024 à 16:20, Willy Tarreau a écrit : On Fri, Jun 14, 2024 at 04:12:03PM +0200, Christopher Faulet wrote: Hi, HAProxy 3.1-dev1 was released on 2024/06/14. It added 95 new commits after version 3.1-dev0. Because Willy announced

Re: [ANNOUNCE] haproxy-3.1-dev1

Le 14/06/2024 à 16:20, Willy Tarreau a écrit : On Fri, Jun 14, 2024 at 04:12:03PM +0200, Christopher Faulet wrote: Hi, HAProxy 3.1-dev1 was released on 2024/06/14. It added 95 new commits after version 3.1-dev0. Because Willy announced publicly I should managed a -dev1 before his return from

Re: [ANNOUNCE] haproxy-3.1-dev1

On Fri, Jun 14, 2024 at 04:12:03PM +0200, Christopher Faulet wrote: > Hi, > > HAProxy 3.1-dev1 was released on 2024/06/14. It added 95 new commits > after version 3.1-dev0. > > Because Willy announced publicly I should managed a -dev1 before his return > from vacations,

[ANNOUNCE] haproxy-3.1-dev1

Hi, HAProxy 3.1-dev1 was released on 2024/06/14. It added 95 new commits after version 3.1-dev0. Because Willy announced publicly I should managed a -dev1 before his return from vacations, I have no choice. So, faced with so much pressure, here is the first 3.1 dev release. After the feature

[ANNOUNCE] haproxy-2.8.10

Hi, HAProxy 2.8.10 was released on 2024/06/14. It added 80 new commits after version 2.8.9. This version is part of the serie of new stable releases which follows the new 3.0. Here is a summary of the most notable changes. Several fixes are applied for better HTTP conformance. In some cases

[ANNOUNCE] haproxy-2.9.9

Hi, HAProxy 2.9.9 was released on 2024/06/14. It added 13 new commits after version 2.9.8. As for the 3.0, an major issue on the H1 multiplexer regarding the H1 requests draining for us to emit a new release just few days after the previous one. This issue could lead to a crash becaues of a use

[ANNOUNCE] haproxy-3.0.2

Hi, HAProxy 3.0.2 was released on 2024/06/14. It added 21 new commits after version 3.0.1. Unfortunately, few days after the previous release, a bug on the H1 multiplexer was found, forcing us to emit a new release. The issue affected the H1 requests draining that could lead to a crash because

[ANNOUNCE] haproxy-2.9.8

Hi, HAProxy 2.9.8 was released on 2024/06/11. It added 106 new commits after version 2.9.7. This release is pretty huge as HAProxy development team was mainly focused on finalizing the new 3.0 version. Now we are catching up the delay and are preparing to emit a serie of new stable releases. I

[ANNOUNCE] haproxy-3.0.1

Hi, HAProxy 3.0.1 was released on 2024/06/10. It added 23 new commits after version 3.0.0. This release fixed the usual bugs that we missed before emitting the 3.0.0. The first one, in the H1 multiplexer, is pretty annoying. It was possible to truncate the first 10 bytes of the first chunk of

Re: [ANNOUNCE] haproxy-3.0.0

Hi Tim, On Wed, May 29, 2024 at 07:48:10PM +0200, Tim Düsterhus wrote: > Hi > > On 5/29/24 17:07, Willy Tarreau wrote: > > HAProxy 3.0.0 was released on 2024/05/29. > > Congratulations on the successful release! Thanks! > I've just opened a PR for the "Offi

Re: [ANNOUNCE] haproxy-3.0.0

Hi On 5/29/24 17:07, Willy Tarreau wrote: HAProxy 3.0.0 was released on 2024/05/29. Congratulations on the successful release! I've just opened a PR for the "Official Docker Images" to add HAProxy 3.1: https://github.com/docker-library/haproxy/pull/234 And of course it wou

[ANNOUNCE] haproxy-3.0.0

Hi, HAProxy 3.0.0 was released on 2024/05/29. It added 21 new commits after version 3.0-dev13. I do appreciate that everything was only cosmetic. We're having a total of 1108 patches in this release among which 850 ones not concerning a bug, which makes it the smallest LTS release of all

  1   2   3   4   5   6   7   8   9   10   >