happening and it appears the entire
HTML header and footer is missing:
Example:
http://www.haproxy.org/bugs/bugs-2.4.html
http://www.haproxy.org/bugs/bugs-2.6.2.html
BR,
Lukas
--
Best regards,
Artur
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
Feature request submitted: https://github.com/haproxy/haproxy/issues/2256
--
Best regards,
Artur
not ready to
work on such a complex project. But if I can help, I'll do.
--
Best regards,
Artur
Hello !
I wonder if there is a roadmap to support WebTransport protocol in haproxy.
There are some explanations/references (if needed) from socket.io dev
team that started to support it :
https://socket.io/get-started/webtransport
--
Best regards,
Artur
Hello Willy,
I understand, thank you for the explanation.
Have a nice holidays ! ;)
Le 07/06/2023 à 14:55, Willy Tarreau a écrit :
Hello Artur,
On Tue, Jun 06, 2023 at 03:18:31PM +0200, Artur wrote:
About the backporting instructions I was not sure how far it should be
backported. I
wrong for all the tests I've made.
--
Best regards,
Artur
explain if this backport instruction is really
required and what to do if one is unsure about how to backport.
Le 06/06/2023 à 14:54, Tim Düsterhus a écrit :
Hi Artur,
On 6/6/23 14:42, Artur wrote:
DOC: quic: fix misspelled tune.quic.socket-owner
Commit 511ddd5 introduced tune.quic.socket
:00 2001
From: Artur Pydo
Date: Tue, 6 Jun 2023 11:49:59 +0200
Subject: [PATCH] DOC: quic: fix misspelled tune.quic.socket-owner
---
doc/configuration.txt | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/doc/configuration.txt b/doc/configuration.txt
index adcd00414..b147b501c
Hello Amaury,
Le 06/06/2023 à 09:30, Amaury Denoyelle a écrit :
On Mon, Jun 05, 2023 at 07:21:37PM +0200, Artur wrote:
Hello,
In the following commit tune.quic.socket-owner parameter is introduced.
However, in configuration.txt, line 4629, it's misspelled as
tune.quic.conn-owner.
https
on github if necessary.
--
Best regards,
Artur
be suitable
for 2.8 version as well...
https://www.haproxy.com/blog/announcing-haproxy-2-6
--
Best regards,
Artur
Hello,
What is suggested/recommended way to get QUIC / HTTP/3 working in
haproxy on Debian ?
--
Best regards,
Artur
backend servers depending the reuse frequency and
the number of threads.
Is this a workaround for the previous versions or one need to apply this
setting also to the current version ?
Thank you for your clarification.
--
Best regards,
Artur
.tcp_keepalive_intvl = 75
net.ipv4.tcp_keepalive_probes = 9
net.ipv4.tcp_keepalive_time = 7200
In my situation I had to change these to something like :
net.ipv4.tcp_keepalive_intvl = 30
net.ipv4.tcp_keepalive_probes = 3
net.ipv4.tcp_keepalive_time = 120
Le 18/10/2022 à 11:15, Artur wrote :
Hello
-on until you get to a connection that is
mostly idle.
*From:* Artur
*Sent:* Tuesday, October 18, 2022 5:15 AM
*To:* haproxy
*Subject:* TCP connections resets during backend transfers
Hello,
While renewing a node.js servers
t doesn't
solve the problem.
--
Best regards,
Artur
allbackups
server sb1 10.100.131.33:2000 cookie s1 backup
server sb2 10.100.131.33:2001 cookie s2 backup
--
Best regards,
Artur
, essentially small bug fixes, QUIC counters
and doc updates.
It's available on haproxy.debian.net. No QUIC support as neither Debian
nor Ubuntu has the appropriate library.
--
Best regards,
Artur
Le 14/03/2022 à 11:40, Christopher Faulet a écrit :
Le 3/14/22 à 10:53, Artur a écrit :
Hello,
I'd like to know how checks behaves depending on the "inter" and
"timeout check" settings.
Let's try this simplified setup :
backend back
mode tcp
timeout check 5s
p to 5 seconds) for this check to finish before
launching another check or it's still launching checks every 2s anyway ?
--
Best regards,
Artur
Hello Tim,
Le 07/06/2021 à 19:13, t...@bastelstu.be a écrit :
> Artur,
>
> [cc'ing Amaury]
>
> Am 2021-06-07 16:46, schrieb Artur:
>> However the only difference is the 443 port explicitly specified in the
>> later request.
>> I am not sure it's something speci
Le 07/06/2021 à 17:22, Jarno Huuskonen a écrit :
> Hello,
>
> On Mon, 2021-06-07 at 16:46 +0200, Artur wrote:
>> Hello,
>>
>> I'm currently running haproxy 2.4.0 and I can see something strange in
>> the way haproxy selects a backend for processing some requests.
never seen it
before.
Is it an expected behaviour ? If so, how can I change my acls to correct
it ?
--
Best regards,
Artur
Hello,
Thank you for this new release.
When can we expect prebuilt packages for Debian on haproxy.debian.net ?
Le 14/05/2021 à 11:56, Willy Tarreau a écrit :
> HAProxy 2.4.0 was released on 2021/05/14.
--
Best regards,
Artur
Hello,
I didn't see any answer or comment on my inquiry.
I supposed that one will say it's not possible or there is a miracle
solution or it may be a new feature. :)
Could you please tell me what would be the right hypothesis ?
Le 01/09/2020 à 11:08, Artur a écrit :
> Hello,
>
> I need
ed
Any idea on how to achieve this ?
--
Best regards,
Artur
hould be fine.
--
Best regards,
Artur
Hello,
It would be nice to have a Debian Stretch package for the current LTS
2.2 branch in backports. It seems it's not available for now.
--
Best regards,
Artur
a loop
> - more importantly, srv->idle_conns and srv->safe_conns are not
> thread-safe list in 2.0 and 2.1
>
> I choose to revert the changes < 2.2
--
Best regards,
Artur
Hi,
Le 17/12/2019 à 17:10, Vincent Bernat a écrit :
>
> I have pushed HAProxy 2.1.1 for Stretch. Tell me if everything is OK for
> you.
I tested also. Everything seems to be OK. Thank you.
--
Best regards,
Artur
ect
http-request set-path /p3%[path] if is_ppds is_question_direct
While using replace-uri, my mistake was to blindly follow the official
documentation examples.
None of these uses absolute uri form.
--
Best regards,
Artur
Hi,
Le 17/12/2019 à 10:28, Vincent Bernat a écrit :
> ❦ 16 décembre 2019 22:15 +01, Artur :
>
>> While checking for haproxy 2.1 package for Debian Stretch on
>> https://haproxy.debian.net/, I saw it wasn't available (yet ?).
>>
>> Do you plan to build haproxy
Hello,
While checking for haproxy 2.1 package for Debian Stretch on
https://haproxy.debian.net/, I saw it wasn't available (yet ?).
Do you plan to build haproxy deb packages for this version of Debian,
it's still supported as oldstable for now ?
--
Best regards,
Artur
Hello Cyril,
Thanks a lot for the confirmation.
Le 16/12/2019 à 20:20, Cyril Bonté a écrit :
> Hi Artur,
>
> Le 16/12/2019 à 19:06, Artur a écrit :
>> Hello,
>>
>> This is an extract of my frontend configuration working perfectly on
>> 2.0.11.
>>
>> f
to the backend.
Once I switched to 2.1.1, haproxy no longer rewrites the URI and the
URIs remains unchanged while forwarded to the backend. I had to
downgrade to have the usual behaviour.
Is it a bug or something changed in normal haproxy behaviour with 2.1
release ?
--
Best regards,
Artur
ll manage logging with
haproxy are welcome. I always had a problem to correctly understand
logging in haproxy.
Thanks a lot for your help.
--
Best regards,
Artur
ile.js HTTP/1.1".
--
Best regards,
Artur
some traffic passing
through the TCP connection.
--
Best regards,
Artur
at different levels?
As I'm here, maybe you have some other suggestions on websocket specific
setup/options tuning?
--
Best regards,
Artur
Hi Jarno,
Thanks a lot. Very helpful. Works very well.
Jarno Huuskonen wrote :
> Hi,
>
> On Tue, Jan 31, Artur wrote:
>> Hello,
>>
>> I'm currently serving public static content from a webserver behind haproxy.
>> What could be the right way to password prot
Hello,
I'm currently serving public static content from a webserver behind haproxy.
What could be the right way to password protect only a single
subdirectory (and all its content) with haproxy ?
/ -> Public
/directory/private -> Password protected
--
Best regards,
Artur
cookie s3
BTW: Thank's a lot for HAProxy, it's a very good software.
--
Best regards,
Artur
43 matches
Mail list logo
