Re: Increase SSL Key Generation after upgrade from 2.4.15 to 2.4.17

Thank you for your reply I think it is related to these changes and the configuration we have for timeouts. http://git.haproxy.org/?p=haproxy-2.4.git;a=commit;h=f5b2c3f1e65f57782afe30981031f122bd8ee24c http://git.haproxy.org/?p=haproxy-2.4.git;a=commit;h=211fc0b5b060bc7b1f83e6514a8ceaeda7e65ee0

[SPAM] 您好：

尊敬的 您好： 接上级通知各部门人员，公司企业邮箱所有用户登录密码将在3天后过期，为避免数据的丢失，进行重新登记，逾时将出现邮箱无法登录使用的情况，按照指引进行操作！谢谢配合请您立即点击登记： (此邮件仅用于通知，无须回复) 此为系统邮件。请勿回复，谢谢。 2022-05-23 14:04:18

Re: [PATCH 1/2] BUG/MEDIUM: tools: Fix `inet_ntop` usage in sa2str

Thanks for catching that.

[PATCH] REGTESTS: Do not use REQUIRE_VERSION for HAProxy 2.5+ (2)

Introduced in: 18c13d3bd MEDIUM: http-ana: Add a proxy option to restrict chars in request header names see also: fbbbc33df REGTESTS: Do not use REQUIRE_VERSION for HAProxy 2.5+ --- reg-tests/http-rules/restrict_req_hdr_names.vtc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff

Re: [PATCH] CLEANUP: tools: Clean up non-QUIC error message handling in str2sa_range()

On Sun, May 22, 2022 at 12:40:58PM +0200, Tim Duesterhus wrote: > If QUIC support is enabled both branches of the ternary conditional are > identical, upsetting Coverity. Move the full conditional into the non-QUIC > preprocessor branch to make the code more clear. > > This resolves GitHub issue

Re: [PATCH 1/2] BUG/MEDIUM: tools: Fix `inet_ntop` usage in sa2str

On Sun, May 22, 2022 at 01:06:27PM +0200, Tim Duesterhus wrote: > The given size must be the size of the destination buffer, not the size of the > (binary) address representation. > > This fixes GitHub issue #1599. > > The bug was introduced in 92149f9a82a9b55c598f1cc815bc330c555f3561 which is

Słowa kluczowe do wypozycjonowania

Dzień dobry, zapoznałem się z Państwa ofertą i z przyjemnością przyznaję, że przyciąga uwagę i zachęca do dalszych rozmów. Pomyślałem, że może mógłbym mieć swój wkład w Państwa rozwój i pomóc dotrzeć z tą ofertą do większego grona odbiorców. Pozycjonuję strony www, dzięki czemu generują

Re: [PATCH 2/2] CLEANUP: tools: Crash if inet_ntop fails in sa2str

On Sun, May 22, 2022 at 01:06:28PM +0200, Tim Duesterhus wrote: > @@ -1374,7 +1374,10 @@ char * sa2str(const struct sockaddr_storage *addr, int > port, int map_ports) > default: > return NULL; > } > - inet_ntop(addr->ss_family, ptr, buffer, sizeof(buffer)); > +

Re: [PATCH v2] CLEANUP: tools: Crash if inet_ntop fails due to ENOSPC in sa2str

On Mon, May 23, 2022 at 09:30:49AM +0200, Tim Duesterhus wrote: > This is impossible, because we pass a destination buffer that is appropriately > sized to hold an IPv6 address. Applied now, thank you Tim! Willy

Re: Paid feature development: TCP stream compression

On 20/05/2022 22:15, Willy Tarreau wrote: On Fri, May 20, 2022 at 12:16:07PM +0100, Mark Zealey wrote: Thanks, we may use this for a very rough proof-of-concept. However we are dealing with millions of concurrent connections, 10-100 million connections per day, so we'd prefer to pay someone to

Re: Peers using heavily single cpu core

Hi Christopher, I've verified that outgoing connections are now spread between multiple threads! Thank you very much! 23 : st=0x000121(cl heopI W:sRa R:srA) tmask=0x8 umask=0x0 owner=0x56219da29280 iocb=0x56219cdc8730(sock_conn_iocb) back=0 cflg=0x0300 fam=ipv4 lport=1024 rport=52046 fe=hap1

Re: Peers using heavily single cpu core

Hi Maciej, On Mon, May 23, 2022 at 08:50:53AM +0200, Maciej Zdeb wrote: > Hi Christopher, > I've verified that outgoing connections are now spread between multiple > threads! Thank you very much! That's really great, thank you for testing! I, too, thought it was worth being merged even this late

[PATCH v2] CLEANUP: tools: Crash if inet_ntop fails due to ENOSPC in sa2str

This is impossible, because we pass a destination buffer that is appropriately sized to hold an IPv6 address. This is related to GitHub issue #1599. --- src/tools.c | 5 - 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/src/tools.c b/src/tools.c index 79d1d5c9b..4ecbdc4d7 100644

Re: [ANNOUNCE] haproxy-2.6-dev11

Hi Ilya, On Tue, May 24, 2022 at 09:53:01AM +0500, ??? wrote: > Hello, > > can we please address https://github.com/haproxy/haproxy/issues/1585 before > final 2.6 ? I thought it was since I replied it was an FP but OK, I pushed a patch to silence it. Thanks, Willy

Re: [ANNOUNCE] haproxy-2.6-dev11

вт, 24 мая 2022 г. в 10:47, Willy Tarreau : > Hi Ilya, > > On Tue, May 24, 2022 at 09:53:01AM +0500, ??? wrote: > > Hello, > > > > can we please address https://github.com/haproxy/haproxy/issues/1585 > before > > final 2.6 ? > > I thought it was since I replied it was an FP but OK, I

Re: [ANNOUNCE] haproxy-2.6-dev11

Hello, can we please address https://github.com/haproxy/haproxy/issues/1585 before final 2.6 ? Ilya сб, 21 мая 2022 г. в 13:11, Willy Tarreau : > Hi, > > HAProxy 2.6-dev11 was released on 2022/05/20. It added 106 new commits > after version 2.6-dev10. > > Yes, there were still too many changes

[PR] chore: Included githubactions in the dependabot config

Dear list! Author: naveen <172697+naveensriniva...@users.noreply.github.com> Number of patches: 1 This is an automated relay of the Github pull request: chore: Included githubactions in the dependabot config Patch title(s): chore: Included githubactions in the dependabot config Link: