Re: Error While deviceatlas compile/make from source

*After installation haproxy not able to start , show below error* [root@govinda opt]# /opt/haproxy-ssl/sbin/haproxy -f /opt/haproxy-ssl/conf/haproxy.cfg [NOTICE] (42915) : haproxy version is 2.8.3-86e043a [NOTICE] (42915) : path to executable is /opt/haproxy-ssl/sbin/haproxy [ALERT](42915)

Re: mux-h2: Backend stream is not fully closed if frontend keeps stream open

On Mon, Sep 18, 2023 at 9:32 AM Christopher Faulet wrote: > Please find a new patch. It should be good ( or better at least :) The provided patch resolves my scenario for both the gRPC server-client as well as the Java client to nginx server. There is an improvement for sure, and HTTP 200 OK is d

Re: Don't Start Your Project Blind - Request an Estimate Today

Hi,Sorry to bother you again,Have you received my emails? We are a cost estimating and architectural service provider.We estimate all types of construction projects including residential, commercial, new build and federal government projects.If you could send me the set of plans, I would love to

Re: Error While deviceatlas compile/make from source

We are almost there, now remains the linkage part to pass. In your /opt/deviceatlas-enterprise-c-3.2 folder, there should be a `include` and a `lib` or a `lib64` folder So for the last command, what needs to be done instead is one of the following (no need to repeat step 1) : make TARGET=linux-gli

Re: Error While deviceatlas compile/make from source

1) cd /opt/deviceatlas-enterprise-c-3.2 cmake . -DCMAKE_INSTALL_PREFIX=/opt/deviceatlas-enterprise-c-3.2 -DCMAKE_C_FLAGS="-std=gnu99" make make install 2) cd haproxy-2.8.3 make TARGET=linux-glibc USE_PCRE=1 USE_OPENSSL=1 USE_ZLIB=1 USE_DEVICEATLAS=1 DEVICEATLAS_INC=/opt/deviceatlas-enterprise-c-3.

Re: Error While deviceatlas compile/make from source

Hi, Since you build the DeviceAtlas library from cmake prior, the following steps are more appropriate : 1/ Inside the deviceatlas-enterprise-c-3.2 folder cmake . -DCMAKE_INSTALL_PREFIX=/opt/deviceatlas-enterprise-c-3.2 -DCMAKE_C_FLAGS="-std=gnu99" make make install 2/ Inside the haproxy-2.8.3 fo

Re: Error While deviceatlas compile/make from source

Thanks for yours prompt reply about deviceatlas-enterprise-c-3.2 error while make after yours suggestion deviceatlas-enterprise-c-3.2 *make *works fine But while using with haproxy-2.8.3 version gives following error [root@govinda opt]# cd haproxy-2.8.3 [root@govinda haproxy-2.8.3]# make TARGET=

Re: Error While deviceatlas compile/make from source

Hi and thanks for your report. Would the following works for you (recommended to work a fresh extracted directory) ? `cmake . -DCMAKE_INSTALL_PREFIX=/opt/deviceatlas-enterprise-c-3.2 -DCMAKE_C_FLAGS="-std=gnu99"` On Mon, 18 Sept 2023 at 18:45, Amol Arote wrote: > Dear Team, > > We are trying

Re: mux-h2: Backend stream is not fully closed if frontend keeps stream open

Le 16/09/2023 à 16:00, Valters Jansons a écrit : On Thu, Sep 14, 2023 at 12:35 PM Christopher Faulet wrote: After a discussion with Willy, we've hopefully found a way to fix the issue by delaying detection of the server abort on the request processing side when there is a response to forward to

Re: [PATCH] MEDIUM: sample: Enhances converter "bytes" to take variable names as arguments

Hello Willy Thanks for the detailed explanations and the feedback. PFA the two patches based on your feedback. My apologies for the delay. Truncation can be useful but I could understand that when extracting bytes > one would want this exact number of bytes to continue the processing. I > just wa

Re: mux-h2: Backend stream is not fully closed if frontend keeps stream open

Yes, that e2e is probably not going to do nasty things. But it worth a try On Sun, Sep 17, 2023, 03:26 Valters Jansons wrote: > On Sat, Sep 16, 2023 at 10:02 PM Илья Шипицин > wrote: > > I wonder if there're gRPC test tests similar to h2spec (I couldn't findI > am them) > > I am not aware of a

Re: mux-h2: Backend stream is not fully closed if frontend keeps stream open

Hi Valters, On Sun, Sep 17, 2023 at 04:25:48AM +0300, Valters Jansons wrote: > But, gRPC is essentially a framework (binary encoding and custom > headers) for object-oriented HTTP/2. My observed issue is an HTTP/2 > processing issue by HAProxy, when the frontend client doesn't send an > END_STREAM

Re: mux-h2: Backend stream is not fully closed if frontend keeps stream open

On Sat, Sep 16, 2023 at 10:02 PM Илья Шипицин wrote: > I wonder if there're gRPC test tests similar to h2spec (I couldn't findI am > them) I am not aware of a single binary that could be used as a gRPC test for proxies. The closest thing that I can think of is examples from official gRPC librar

Re: mux-h2: Backend stream is not fully closed if frontend keeps stream open

I wonder if there're gRPC test tests similar to h2spec (I couldn't find them) сб, 16 сент. 2023 г. в 18:06, Valters Jansons : > On Thu, Sep 14, 2023 at 12:35 PM Christopher Faulet > wrote: > > After a discussion with Willy, we've hopefully found a way to fix the > issue by > > delaying detection

Re: mux-h2: Backend stream is not fully closed if frontend keeps stream open

On Thu, Sep 14, 2023 at 12:35 PM Christopher Faulet wrote: > After a discussion with Willy, we've hopefully found a way to fix the issue by > delaying detection of the server abort on the request processing side when > there > is a response to forward to the client. It should do the trick in your

Re: Patch sample_conv_json_query in sample.c to return array values

Dear Jens. Please can you create a patch as mentioned in https://github.com/haproxy/haproxy/blob/master/CONTRIBUTING as suggested in https://github.com/haproxy/haproxy/issues/2281#issuecomment-1721014384 Regards Alex On 2023-09-15 (Fr.) 14:57, Jens Popp wrote: Hi, currently the method samp

RE: [PATCH 4/4] MEDIUM: tcp-act: Add new set-tlv TCP action for PPv2 TLVs

From da4dc50153fe6cc7e562b63439dd8be4846e0dcf Mon Sep 17 00:00:00 2001 From: Alexander Stephan Date: Fri, 15 Sep 2023 12:25:03 +0200 Subject: [PATCH 4/4] MEDIUM: tcp-act: Add new set-tlv TCP action for PPv2 TLVs This commit adds an action called set-tlv() that allows to directly update the TLV d

RE: [PATCH 3/4] LOW: connection: Add TLV update function

From cc8fe58a8d2f8d47b03d03fd1048fe1b9babca70 Mon Sep 17 00:00:00 2001 From: Alexander Stephan Date: Fri, 15 Sep 2023 12:18:10 +0200 Subject: [PATCH 3/4] LOW: connection: Add TLV update function Until now, it was not possible to deliberatily change received TLVs that are stored within a connectio

RE: [PATCH 2/4] MEDIUM: connection: Send out generically allocated proxy-v2-options

From 84608ed754c1a92e85e03036e8b0cd0949721ffb Mon Sep 17 00:00:00 2001 From: Alexander Stephan Date: Fri, 15 Sep 2023 12:42:36 +0200 Subject: [PATCH 2/4] MEDIUM: connection: Send out generically allocated proxy-v2-options This commit removes the previous limitations on the existing, fixed PPv2 T

RE: [PATCH 1/4] MEDIUM: server: Parse generic type-value pairs as proxy-v2-options

From fb8714c5aebd7fe957264d0f2234182f55f952fe Mon Sep 17 00:00:00 2001 From: Alexander Stephan mailto:alexander.step...@sap.com>> Date: Fri, 15 Sep 2023 12:38:46 +0200 Subject: [PATCH 1/4] MEDIUM: server: Parse generic type-value pairs as proxy-v2-options This commit introduces a generic server-

Re: HAProxy and musl (was: Re: HAproxy Error)

Hi. Resuscitate this old thread with a musl lib update. https://musl.libc.org/releases.html ``` musl-1.2.4.tar.gz (sig) - May 1, 2023 This release adds TCP fallback to the DNS stub resolver, fixing the longstanding inability to query large DNS records and incompatibility with recursive n

Re: mux-h2: Backend stream is not fully closed if frontend keeps stream open

Le 14/09/2023 à 01:36, Valters Jansons a écrit : I set up a small PoC repository at https://github.com/sigv/grpcopen with a server and a client. There is a Ping endpoint, which works fine (the frontend client is first to close). There is also a Foobar endpoint, which is intentionally mangled, to

Re: mux-h2: Backend stream is not fully closed if frontend keeps stream open

> As annoying as it can be, this is also expected in order not to break > uploads. For example if you have an H2->H1 gateway after haproxy, > interrupting the upload before the end would require to break the > connection, which can be particularly expensive (i.e. need to close >

Re: SV: HaProxy does not updating DNS cache

Hi Henning, On Wed, Sep 13, 2023 at 05:54:46PM +, Henning Svane wrote: > Hi > > Thanks for your answer. > > It is in the frontend I used the "dynamic" DNS. > > Will the resolver also be used in the frontend section? > > Because I only can see examples for backend servers. Could you pleas

Re: HaProxy does not updating DNS cache

Hi. On 2023-09-13 (Mi.) 14:39, Henning Svane wrote: Hi I have tried using a DNS with a TTL of 600 sec. and the DNS changes once in a while, but every time I have to restart Haproxy to get the updated DNS to work. Even if I wait for hours. I can see with nslookup that the server can see the

Re: HaProxy does not updating DNS cache

On Wed, Sep 13, 2023 at 12:39:36PM +, Henning Svane wrote: > Hi > > I have tried using a DNS with a TTL of 600 sec. and the DNS changes > once in a while, but every time I have to restart Haproxy to get the > updated DNS to work. Even if I wait for hours. I can see with > nslookup that the se

Re: mux-h2: Backend stream is not fully closed if frontend keeps stream open

rder not to break uploads. For example if you have an H2->H1 gateway after haproxy, interrupting the upload before the end would require to break the connection, which can be particularly expensive (i.e. need to close and re-establish a new one for next request) and even be abused for denial

Re: [PATCH] BUG/MINOR: promex: fix backend_agg_check_status

Le 12/09/2023 à 11:37, Cedric Paillet a écrit : When a server is in maintenance, the check.status is no longer updated. Therefore, we shouldn't consider check.status if the checks are not active. This check was properly implemented in the haproxy_server_check_status metric, but wasn't carried

RE: [PATCH] BUG/MINOR: promex: don't count servers in maintenance

it afterwards. Thank you very much. -Message d'origine- De : Christopher Faulet Envoyé : lundi 11 septembre 2023 20:15 À : Cedric Paillet ; haproxy@formilux.org Objet : Re: [PATCH] BUG/MINOR: promex: don't count servers in maintenance Le 07/09/2023 à 16:50, Cedric Paillet a écrit 

Re: [PATCH] MINOR: promex: Introduce 'FULL' status for srv_state metric

On Mon, Sep 11, 2023 at 08:39:30PM +0200, Christopher Faulet wrote: > Le 11/09/2023 à 15:12, Cedric Paillet a écrit : > > This adds a new 'FULL' status to the Prometheus metric 'srv_state'. It > > helps identify servers that have exceeded their maxconn limit and cannot > > accept new connections.

Re: [PATCH] MINOR: promex: Introduce 'FULL' status for srv_state metric

Le 11/09/2023 à 15:12, Cedric Paillet a écrit : This adds a new 'FULL' status to the Prometheus metric 'srv_state'. It helps identify servers that have exceeded their maxconn limit and cannot accept new connections. Rename server_has_room to !server_is_full to matches what's used at a few place

Re: [PATCH] BUG/MINOR: promex: don't count servers in maintenance

Le 07/09/2023 à 16:50, Cedric Paillet a écrit : And I guess we should also check the healthchecks are enabled for the server. It is not really an issue because call to get_check_status_result() will exclude neutral and unknown satuses. But there is no reason to count these servers. What we

Re: [PATCH] BUG/MINOR: promex: don't count servers in maintenance

Le 11/09/2023 à 15:09, Cedric Paillet a écrit : The state of servers that were put in maintenance via the runtime API are reported within the "backend_agg_check_status" metric, which lead to inconsistent sums when compared to the "haproxy_server_check_status" metric. Now excluding them from this

Re: [PATCH] MEDIUM: sample: Implement sample fetch for arbitrary PROXY protocol v2 TLV values

Hi Alexander, On Mon, Sep 11, 2023 at 03:44:16PM +, Stephan, Alexander wrote: > Hi Willy and Ilya, > > Sorry for the absence, I was mostly out-of-office the last week. I am really > sorry for causing this bug. No worries, stuff like this happens, that's why we have regtests, CI, this develop

RE: [PATCH] MEDIUM: sample: Implement sample fetch for arbitrary PROXY protocol v2 TLV values

, Alexander From: Илья Шипицин Sent: Thursday, August 31, 2023 8:56 PM To: Willy Tarreau Cc: Stephan, Alexander ; haproxy@formilux.org Subject: Re: [PATCH] MEDIUM: sample: Implement sample fetch for arbitrary PROXY protocol v2 TLV values You don't often get email from chipits...@gmai

Re: Odd bwlim Behavior

Le 08/09/2023 à 14:51, Luke Seelenbinder a écrit : Hi Christopher, I just tried with a single limit on a single table (50m per 10s). Unfortunately, it looks like the behavior persists. Interestingly enough…the an_exp in this case is now 12m! Hi Like, 12min is amazingly high ! Could you sh

Re: [PATCH 0/2] CI: musl pipeline improvement

On Wed, Sep 06, 2023 at 07:04:47PM +0200, Ilya Shipitsin wrote: > it has been figured out that it is hard to find gdb backtraces on musl, > because > corresponding section is not highlighted. let us fix that Now merged, thank you Ilya! Willy

Re: [PATCH] MEDIUM: sample: Enhances converter "bytes" to take variable names as arguments

On Thu, Sep 07, 2023 at 10:45:58AM -0700, Lokesh Jindal wrote: > Resending the patch with the right email subject. Previos email > discussion - here > . I saw your previous mail, just didn't have time yet to review it. > PFA the pat

Re: Odd bwlim Behavior

Hi Christopher, I just tried with a single limit on a single table (50m per 10s). Unfortunately, it looks like the behavior persists. Interestingly enough…the an_exp in this case is now 12m! 0x558271832070: [08/Sep/2023:11:47:38.760889] id=7741 proto=quic6 source=CLIENT:51574 flags=0x100c4a,

Re: Odd bwlim Behavior

Le 08/09/2023 à 13:42, Luke Seelenbinder a écrit : Hi Christopher, Thanks for the hint. I was able to replicate it and capture the following from `show sess all`: 0x562d78315da0: [08/Sep/2023:11:33:40.093147] id=32890 proto=tcpv4 source=:34452   flags=0x100c4a, conn_retries=0, conn_exp= con

Re: Odd bwlim Behavior

Hi, A few more details (replicated it a few more times). Here's curl output (with timestamps): 11:54:13.155873 * Trying 2400:8902:e001:2df::1:443... 11:54:13.155994 * Connected to tiles.stadiamaps.com (2400:8902:e001:2df::1) port 443 (#0) 11:54:13.156419 * ALPN, offering h2 11:54:13.156434 *

Re: Odd bwlim Behavior

Hi Christopher, Thanks for the hint. I was able to replicate it and capture the following from `show sess all`: 0x562d78315da0: [08/Sep/2023:11:33:40.093147] id=32890 proto=tcpv4 source=:34452 flags=0x100c4a, conn_retries=0, conn_exp= conn_et=0x000 srv_conn=0x562d77d74d60, pend_pos=(nil) wai

RE: [PATCH] BUG/MINOR: promex: don't count servers in maintenance

> I guess you mean "backend_add_check_status". Because > "backend_agg_server_check_status" is a deprecated metric. It was replaced by > "backend_agg_server_status". Yes, sorry (and I should know, it's me who deprecated this value! 😊)" In this patch both will be up updated, as it's the same code !

Re: Odd bwlim Behavior

Le 07/09/2023 à 14:52, Luke Seelenbinder a écrit : Could this fix: > BUG/MEDIUM: h1-htx: Ensure chunked parsing with full output buffer have caused this issue with bwlim? I was only able to replicate the behavior in HTTP/1.1. If your responses are chunked, it is possible. But only for res

Re: [PATCH] BUG/MINOR: promex: don't count servers in maintenance

Hi, Thanks Cedric and sorry for the delay. I have few comments. Le 01/09/2023 à 08:22, Cedric Paillet a écrit : The state of servers that were put in maintenance via the runtime API are reported within the "backend_agg_server_check_status" metric, which I guess you mean "backend_add_check_statu

Re: Odd bwlim Behavior

Could this fix: > BUG/MEDIUM: h1-htx: Ensure chunked parsing with full output buffer have caused this issue with bwlim? I was only able to replicate the behavior in HTTP/1.1. Best, Luke — Luke Seelenbinder Stadia Maps | Founder & CEO stadiamaps.com > On Sep 2, 2023, at 16:02, Luke Seelenbinde

Re: Haproxy 2.8 with Proxy Protocol v2 does not close connections

On Thu, 7 Sept 2023 at 14:03, Tom Braarup wrote: > > Hello, > > After upgrading Haproxy from 2.7 to 2.8, with Nginx (1.25.0) as > backends and Proxy Protocol v2, the connections are not closed, > CLOSE_WAIT is increasing over time. No configuration changes apart from > the Haproxy version. 2.8.3

Re: [PATCH] BUILD: ssl: Build with new cryptographic library AWS-LC

; > > *From: *Илья Шипицин > *Date: *Wednesday, September 6, 2023 at 5:41 AM > *To: *William Lallemand > *Cc: *"Hopkins, Andrew" , Willy Tarreau , > Aleksandar Lazic , "haproxy@formilux.org" < > haproxy@formilux.org> > *Subject: *RE: [EXTERNAL] [PAT

RE: [PATCH 0/1] Introduce 'NOROOM' status for srv_state metric

nd OK. We risk missing it, not necessarily capturing the value at the right time. Cedric -Message d'origine- De : Willy Tarreau Envoyé : mercredi 6 septembre 2023 10:36 À : Cedric Paillet Cc : haproxy@formilux.org Objet : Re: [PATCH 0/1] Introduce 'NOROOM' status for srv_sta

Re: [PATCH] BUILD: ssl: Build with new cryptographic library AWS-LC

zic , "haproxy@formilux.org" Subject: RE: [EXTERNAL] [PATCH] BUILD: ssl: Build with new cryptographic library AWS-LC CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you can confirm the sender and know the content is safe. ba

Re: [PATCH] BUILD: ssl: Build with new cryptographic library AWS-LC

Thanks for looking at this. I couldn't figure out what in CodeBuild was sending a different signal to the processes so I moved the HAPRoxy job to GitHub actions like your CI in https://github.com/aws/aws-lc/pull/1174 and it's all passing over here too! On 9/6/23, 5:26 AM, "William Lallemand" m

Re: Request for feedback: Add support for txn args as arguments in converter "bytes"

PFA the patch. I have two questions: 1. Can you explain what this method does and why is it needed? (I used it in my patch following the pattern in the converter "sub") - *smp_set_owner(&smp_arg0, smp->px, smp->sess, smp->strm, smp->opt);* 2. In my patch, *sample_conv_bytes* returns 0 in case of a

Re: [PATCH] CI: Update to actions/checkout@v4

Hi Tim! On Wed, Sep 06, 2023 at 04:57:29PM +0200, Tim Duesterhus wrote: > No functional change, but we should keep this current. Now merged, thank you! Willy

Re: [PATCH 0/1] Introduce 'NOROOM' status for srv_state metric

On Wed, Sep 06, 2023 at 12:44:56PM +, Cedric Paillet wrote: > >I think that it might be more suitable to use the term "FULL" > Ok, no problem with that. (Perhaps we can also rename server_has_room to > !server_is_full ?) You're right, it might be clearer! > > Also, a more accurate metric tha

RE: [PATCH 0/1] Introduce 'NOROOM' status for srv_state metric

LL" will the backend queue start to grow, correct? Cédric -Message d'origine- De : Willy Tarreau Envoyé : mercredi 6 septembre 2023 10:36 À : Cedric Paillet Cc : haproxy@formilux.org Objet : Re: [PATCH 0/1] Introduce 'NOROOM' status for srv_state metric Hi Cedric, On

Re: [PATCH] BUILD: ssl: Build with new cryptographic library AWS-LC

based on USE_OPENSSL_AWSLC quic may be enabled ? ср, 6 сент. 2023 г. в 14:26, William Lallemand : > On Tue, Sep 05, 2023 at 11:56:26PM +, Hopkins, Andrew wrote: > > I split up the remaining CI changes into 4 new attached patches. The > > latest changes are still passing on my fork > > https:

Re: [PATCH] BUILD: ssl: Build with new cryptographic library AWS-LC

On Tue, Sep 05, 2023 at 11:56:26PM +, Hopkins, Andrew wrote: > I split up the remaining CI changes into 4 new attached patches. The > latest changes are still passing on my fork > https://github.com/andrewhop/haproxy/actions/runs/6090899582. > Thanks, I just merged them! > I was hoping to t

Re: [PATCH 0/1] Introduce 'NOROOM' status for srv_state metric

Hi Cedric, On Tue, Sep 05, 2023 at 01:40:14PM +, Cedric Paillet wrote: > We are using Prometheus to provide feedback to our users about the status of > backend servers. Currently, we have no means of informing them if a server > exceeds the maxconn limit, and consequently why it's no longer re

Re: [PATCH] BUILD: ssl: Build with new cryptographic library AWS-LC

I split up the remaining CI changes into 4 new attached patches. The latest changes are still passing on my fork https://github.com/andrewhop/haproxy/actions/runs/6090899582. I was hoping to take advantage of the better HAProxy support in AWS-LC's CI but I'm running into some issues in https://

Re: [PATCH] BUILD: ssl: Build with new cryptographic library AWS-LC

On Fri, Sep 01, 2023 at 01:25:55AM +, Hopkins, Andrew wrote: > Hi, Hi Andrew! > I have what I think it approaching the final 3 patches attached. I > cleaned up the first patch so it just includes the code, makefile, and > documentation changes to support AWS-LC. The second patch disables the

Re: [PATCH] MINOR: properly mark the end of the CLI command in error messages

On Sat, Sep 02, 2023 at 10:05:11AM +0200, Miroslav Zagorac wrote: > Hello all, > > this is a patch related to correctly marking the end of the CLI command in the > error message in several places in the file src/ssl_ckch.c . > Thanks, merged. -- William Lallemand

Re: Odd bwlim Behavior

One other detail: we're on the latest 2.8.2 version. — Luke Seelenbinder Stadia Maps | Founder & CEO stadiamaps.com > On Sep 2, 2023, at 15:56, Luke Seelenbinder > wrote: > > Hi List, > > I wanted to ask about an unexpected behavior I'm observing with the bandwidth > limit filter. I'm not su

Re: [PATCH] BUILD: ssl: Build with new cryptographic library AWS-LC

Hi, I have what I think it approaching the final 3 patches attached. I cleaned up the first patch so it just includes the code, makefile, and documentation changes to support AWS-LC. The second patch disables the one FFDH test when HAPRoxy is build with AWS-LC. Finally, the third patch does a fe

Re: [PATCH] MEDIUM: sample: Implement sample fetch for arbitrary PROXY protocol v2 TLV values

cirrus-ci backtrace freebsd (cirrus-ci) crash · Issue #2275 · haproxy/haproxy (github.com) as usual, I'll send CI improvements once polished чт, 31 авг. 2023 г. в 18:22, Илья Шипицин : > while trying to enable "gdb bt" on cirrus-ci, I noticed tha

Re: [PATCH] MEDIUM: sample: Implement sample fetch for arbitrary PROXY protocol v2 TLV values

while trying to enable "gdb bt" on cirrus-ci, I noticed that we have similar crashes on musl (where gdb implemented already) https://github.com/haproxy/haproxy/issues/2274 ср, 30 авг. 2023 г. в 05:29, Willy Tarreau : > On Tue, Aug 29, 2023 at 11:16:32PM +0200, ??? wrote: > > ??, 29 ???.

Re: [PATCH] MEDIUM: sample: Implement sample fetch for arbitrary PROXY protocol v2 TLV values

On Tue, Aug 29, 2023 at 11:16:32PM +0200, ??? wrote: > ??, 29 ???. 2023 ?. ? 16:45, Willy Tarreau : > > > On Tue, Aug 29, 2023 at 04:31:31PM +0200, Willy Tarreau wrote: > > > On Tue, Aug 29, 2023 at 02:16:55PM +, Stephan, Alexander wrote: > > > > However, I noticed there is a problem

Re: [PATCH] MEDIUM: sample: Implement sample fetch for arbitrary PROXY protocol v2 TLV values

вт, 29 авг. 2023 г. в 16:45, Willy Tarreau : > On Tue, Aug 29, 2023 at 04:31:31PM +0200, Willy Tarreau wrote: > > On Tue, Aug 29, 2023 at 02:16:55PM +, Stephan, Alexander wrote: > > > However, I noticed there is a problem now with the FreeBSD test. Have > you > > > already looked into it? > >

Re: [PATCH] MEDIUM: sample: Implement sample fetch for arbitrary PROXY protocol v2 TLV values

On Tue, Aug 29, 2023 at 04:31:31PM +0200, Willy Tarreau wrote: > On Tue, Aug 29, 2023 at 02:16:55PM +, Stephan, Alexander wrote: > > However, I noticed there is a problem now with the FreeBSD test. Have you > > already looked into it? > > Ah no, I had not noticed. I first pushed into a tempora

Re: [PATCH] MEDIUM: sample: Implement sample fetch for arbitrary PROXY protocol v2 TLV values

On Tue, Aug 29, 2023 at 02:16:55PM +, Stephan, Alexander wrote: > However, I noticed there is a problem now with the FreeBSD test. Have you > already looked into it? Ah no, I had not noticed. I first pushed into a temporary branch and everything was OK so I pushed into master again without che

RE: [PATCH] MEDIUM: sample: Implement sample fetch for arbitrary PROXY protocol v2 TLV values

Hi Willy, > And I was wrong, they were indeed for the first one. However I had to also > remove the NOT_LAST from the intermediate patches using the list_for_each(). > I put quotes around the symbolic names in the doc to make it clearer which > one was to be used and which one it corresponds to

Re: [PATCH] MEDIUM: sample: Implement sample fetch for arbitrary PROXY protocol v2 TLV values

On Tue, Aug 29, 2023 at 03:15:48PM +0200, Willy Tarreau wrote: > Overall yes. There are just two small parts in the first patch that are > for the immediately following patches ("refactor...") that I'm going to > move there. And I was wrong, they were indeed for the first one. However I had to als

Re: [PATCH] MEDIUM: sample: Implement sample fetch for arbitrary PROXY protocol v2 TLV values

Hi Alexander, On Mon, Aug 28, 2023 at 12:38:45PM +, Stephan, Alexander wrote: > > I'm fine with this, however I find that the doc is not very clear about > > what is permitted > I agree that doc needs some more details. I added the note about the > iterations and described all the symbolic con

Re: how to upgrade haproxy

Hi. On 2023-08-28 (Mo.) 22:30, Atharva Shripad Dudwadkar wrote: Hi Haproxy team, Can we install haproxy using source code in ubuntu 20.04 and how ? You can follow the Install file to compile HAProxy. https://git.haproxy.org/?p=haproxy.git;a=blob;f=INSTALL;h=8492a4f37208a6099629101466fec3378

Re: how to upgrade haproxy

Hi Haproxy team, Can we install haproxy using source code in ubuntu 20.04 and how ? On Thu, 24 Aug 2023 at 4:00 PM, Aleksandar Lazic wrote: > Hi Atharva Shripad Dudwadkar. > > On 2023-08-24 (Do.) 12:08, Willy Tarreau wrote: > > Hi, > > > > On Thu, Aug 24, 2023 at 03:23:59PM +0530, Atharva Shri

Re: Request for feedback: Add support for txn args as arguments in converter "bytes"

Thanks for the response and the corrections, Willy. *We need to decide what to do when the variable does not* *exist or is empty. We can't make converters fail for now, so most likelyit will have to end up as value zero for offset and/or length*. Here is the implementation today - link

RE: [PATCH] MEDIUM: sample: Implement sample fetch for arbitrary PROXY protocol v2 TLV values

Hi Willy, > finally back to this! Overall it's a great and very clean series, I really > want to thank you for this high quality work! Thanks for the compliment, really glad to hear! :) > Yeah it initially gave me a bit of head scratching when reading this part but > I understood what you did a

Re: Request for feedback: Add support for txn args as arguments in converter "bytes"

Hi Lokesh, On Fri, Aug 25, 2023 at 01:44:48PM -0700, Lokesh Jindal wrote: > Hey folks > > I am writing to gather feedback on an idea before doing the implementation. > Per the documentation, converter "bytes" accepts integer values as > arguments, but not txn args. > i.e. ,bytes(2,8) will work >

Re: [PATCH] MEDIUM: sample: Implement sample fetch for arbitrary PROXY protocol v2 TLV values

Hi Alexander, finally back to this! Overall it's a great and very clean series, I really want to thank you for this high quality work! On Wed, Aug 16, 2023 at 04:24:21PM +, Stephan, Alexander wrote: > I was not able to use a check function for authority and unique_id without > modifying sampl

Re: [ANNOUNCE] haproxy-2.9-dev4

On Fri, Aug 25, 2023 at 07:35:12PM +0200, Willy Tarreau wrote: > Hi, > > HAProxy 2.9-dev4 was released on 2023/08/25. It added 59 new commits > after version 2.9-dev3. (...) Please just note that there was a regression in the H2 mux that caused it to crash twice on haproxy.org. I've just fixed it

Re: [ANNOUNCE] haproxy-2.9-dev4

On Fri, Aug 25, 2023 at 08:52:00PM +0200, Aleksandar Lazic wrote: > Looks like that "Reverse HTTP Transport" will be only possible with H2 & H3 > for now, right. This looks then to me that quic + H3 will be implemented > also for server as "proto h3", right? No, it's only H2 for now. And indeed se

Re: [ANNOUNCE] haproxy-2.9-dev4

Hi. On 2023-08-25 (Fr.) 19:35, Willy Tarreau wrote: Hi, HAProxy 2.9-dev4 was released on 2023/08/25. It added 59 new commits after version 2.9-dev3. Some interesting new stuff continues to arrive in this version: [snipp] - reverse HTTP: see below for a complete description. I hope it w

Re: [PATCH] MEDIUM: sample: Implement sample fetch for arbitrary PROXY protocol v2 TLV values

Hi Alexander, On Fri, Aug 25, 2023 at 09:34:08AM +, Stephan, Alexander wrote: > Hi Willy, > > Did you already have the chance to take a look at the updated patches? > No hurry though, I just wanted to make sure that the message didn't get lost. Not yet, I'm still burried under annoying bugs

RE: [PATCH] MEDIUM: sample: Implement sample fetch for arbitrary PROXY protocol v2 TLV values

Hi Willy, Did you already have the chance to take a look at the updated patches? No hurry though, I just wanted to make sure that the message didn't get lost. As mentioned, I am aware that sending individual patches is better in the common case. If that is a problem here, please just let me know

Re: [PATCH 1/1] CI: fedora: fix "dnf" invocation syntax

On Fri, Aug 25, 2023 at 08:20:24AM +0200, Ilya Shipitsin wrote: > In 39e205302e8afb68d954e17944fad5f8c1587287 I erroneously used > "dnf git" instead of "dnf install" > --- > .github/workflows/fedora-rawhide.yml | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > diff --git a/.github/workf

Re: how to upgrade haproxy

Hi Atharva Shripad Dudwadkar. On 2023-08-24 (Do.) 12:08, Willy Tarreau wrote: Hi, On Thu, Aug 24, 2023 at 03:23:59PM +0530, Atharva Shripad Dudwadkar wrote: Hi haproxy Team, Can you please help me with the upgrading process regarding haproxy from 2.0.7 to 2.5. in RHEL. Could you please share

Re: how to upgrade haproxy

Hi, On Thu, Aug 24, 2023 at 03:23:59PM +0530, Atharva Shripad Dudwadkar wrote: > Hi haproxy Team, > > Can you please help me with the upgrading process regarding haproxy from > 2.0.7 to 2.5. in RHEL. Could you please share with me upgrading process? Please note that 2.5 is no longer supported, i

Re: [PR] Fix build error on ppc64le: invalid parameter combination for AltiVec...

On Mon, Aug 21, 2023 at 06:51:00PM +0200, Willy Tarreau wrote: > Hi Tim, Peter, > > On Mon, Aug 21, 2023 at 05:36:58PM +0200, Tim Düsterhus wrote: > > Peter, > > > > On 8/21/23 17:23, PR Bot wrote: > > > Patch title(s): > > > Fix build error on ppc64le: invalid parameter combination for AltiV

Re: [PATCH] BUILD: ssl: Build with new cryptographic library AWS-LC

Hello, On Fri, Aug 18, 2023 at 11:32:17PM +, Hopkins, Andrew wrote: > Do you have a preference between 1 and 2? Where does that notification > go if something does break in the future? I prefer that we only do a weekly build for now, we already have too much things in the per push CI. The fai

Re: [PR] Fix build error on ppc64le: invalid parameter combination for AltiVec...

Hi Tim, Peter, On Mon, Aug 21, 2023 at 05:36:58PM +0200, Tim Düsterhus wrote: > Peter, > > On 8/21/23 17:23, PR Bot wrote: > > Patch title(s): > > Fix build error on ppc64le: invalid parameter combination for AltiVec > > intrinsic __builtin_vec_ld > > > > xxhash.h should not be modified, b

Re: [PR] Fix build error on ppc64le: invalid parameter combination for AltiVec…

Peter, On 8/21/23 17:36, Tim Düsterhus wrote: Petter, Please apologize the typo here. It should read "Peter", of course. Best regards Tim Düsterhus

Re: [PR] Fix build error on ppc64le: invalid parameter combination for AltiVec…

Petter, On 8/21/23 17:23, PR Bot wrote: Patch title(s): Fix build error on ppc64le: invalid parameter combination for AltiVec intrinsic __builtin_vec_ld xxhash.h should not be modified, because it is an external library. However it appears that this might already be fixed upstream [1],

Re: [ANNOUNCE] haproxy-2.4.24

On Sat, Aug 19, 2023 at 12:07:03PM +0200, Willy Tarreau wrote: > - the "namespace" keyword in default-servers was parsed but ignored > > - the duplicate stick-table name check did not work for tables declared > inside peers sections. Sorry, these two ones are copy-paste mistakes in the re

Re: [PATCH] BUILD: ssl: Build with new cryptographic library AWS-LC

Hi Andrew, On Fri, Aug 18, 2023 at 11:32:17PM +, Hopkins, Andrew wrote: > Do you have a preference between 1 and 2? Where does that notification go if > something does break in the future? I have added a dedicated > USE_OPENSSL_AWSLC in the updated > 0001-BUILD-ssl-Build-with-new-cryptographi

Re: [PATCH] BUILD: ssl: Build with new cryptographic library AWS-LC

" Cc: William Lallemand , Willy Tarreau , Aleksandar Lazic , "haproxy@formilux.org" Subject: RE: [EXTERNAL] [PATCH] BUILD: ssl: Build with new cryptographic library AWS-LC CAUTION: This email originated from outside of the organization. Do not click links or open attach

Re: Fast and Professional Estimating Services

 Hi,I wanted to follow up with you regarding our construction estimating services. We specialize in providing detailed and accurate estimates to keep your projects running smoothly and on budget.If you have any upcoming projects that could benefit from our services, please send us the plans. Tha

RE: Cyber Security Software Users

Hi, I was hoping to hear back from you! Did you get a chance to review my previous email? Kindly let me know your current email list requirements, so that I can get back to you accordingly. Look forward to hearing from you soon. Best regards, Janet Talley|Lead Generation Specialist From: Janet

Re: WebTransport support/roadmap

Le 17/08/2023 à 11:46, Aleksandar Lazic a écrit : On 2023-08-17 (Do.) 10:14, Artur wrote: Feature request submitted: https://github.com/haproxy/haproxy/issues/2256 Thank you. I have added a simple picture based on your E-Mails, hope I have understood your request properly. Sorry, I was not

Re: WebTransport support/roadmap

Hi. On 2023-08-17 (Do.) 10:14, Artur wrote: Feature request submitted: https://github.com/haproxy/haproxy/issues/2256 Thank you. I have added a simple picture based on your E-Mails, hope I have understood your request properly. Regards Alex

Re: WebTransport support/roadmap

Feature request submitted: https://github.com/haproxy/haproxy/issues/2256 -- Best regards, Artur

Re: [PATCH] BUILD: ssl: Build with new cryptographic library AWS-LC

023 at 11:26 PM > *To: *William Lallemand > *Cc: *Willy Tarreau , "Hopkins, Andrew" , > Aleksandar Lazic , "haproxy@formilux.org" < > haproxy@formilux.org> > *Subject: *RE: [EXTERNAL] [PATCH] BUILD: ssl: Build with new > cryptographic library AWS-LC >

<    4   5   6   7   8   9   10   11   12   13   >