Re: USE_QUIC=1 support for awslc

On 1/24/24 05:58, Yaacov Akiba Slama wrote: > So right now, the only thing missing in aws_lc in order to fully support > quic is the implementation of EVP_chacha20() ? This is one of the *identified* things which are missing in addition to TLS_AES_128_CCM_SHA256 which cannot be enabled. This does

Re: USE_QUIC=1 support for awslc

On 1/15/24 17:16, Yaacov Akiba Slama wrote: > On 04/10/2023 18:38, William Lallemand wrote: >> Hello, >> >> I fixed the build for USE_QUIC=1 and AWSLC which is limited like Ilya >> mentionned. >> >> For now: >> >>     - 0RTT was disabled. >>     - TLS1_3_CK_CHACHA20_POLY1305_SHA256,

Re: USE_QUIC=1 support for awslc

On 1/17/24 00:53, Hopkins, Andrew wrote: > AWS-LC recently plumbed support for ChaChaPoly and AES CCM through the > existing EVP_CIPHER API that HAProxy uses in > https://github.com/aws/aws-lc/pull/1311 and > https://github.com/aws/aws-lc/pull/1373. Do you need support for just the > cipher

Re: USE_QUIC=1 support for awslc

On 1/16/24 14:25, Frederic Lecaille wrote: > On 1/15/24 17:16, Yaacov Akiba Slama wrote: >> On 04/10/2023 18:38, William Lallemand wrote: >>> Hello, >>> >>> I fixed the build for USE_QUIC=1 and AWSLC which is limited like Ilya >>> mentionned. >

Re: USE_QUIC=1 support for awslc

On 1/15/24 17:16, Yaacov Akiba Slama wrote: > On 04/10/2023 18:38, William Lallemand wrote: >> Hello, >> >> I fixed the build for USE_QUIC=1 and AWSLC which is limited like Ilya >> mentionned. >> >> For now: >> >>     - 0RTT was disabled. >>     - TLS1_3_CK_CHACHA20_POLY1305_SHA256,

Re: USE_QUIC=1 support for awslc

On 1/15/24 17:16, Yaacov Akiba Slama wrote: > On 04/10/2023 18:38, William Lallemand wrote: >> Hello, >> >> I fixed the build for USE_QUIC=1 and AWSLC which is limited like Ilya >> mentionned. >> >> For now: >> >>     - 0RTT was disabled. >>     - TLS1_3_CK_CHACHA20_POLY1305_SHA256,

Re: unsupported protocol family 2 for address 'quic4@0.0.0.0:4

On 11/8/23 13:37, Frederic Lecaille wrote: > On 11/8/23 11:27, Christoph Kukulies wrote: >> parsing [/etc/haproxy/haproxy.cfg:60] : 'bind' : unsupported protocol >> family 2 for address 'quic4@0.0.0.0 <mailto:quic4@0.0.0.0>:4> >> Nov 08 11:16:54 mail. >> >

Re: unsupported protocol family 2 for address 'quic4@0.0.0.0:4

On 11/8/23 11:27, Christoph Kukulies wrote: > parsing [/etc/haproxy/haproxy.cfg:60] : 'bind' : unsupported protocol > family 2 for address 'quic4@0.0.0.0 :4> > Nov 08 11:16:54 mail. > > > I'm using sample.haproxy.cfg from Shawns haproxy-scripts and there the line: > > bind

Fwd: couple of questions on QUIC Interop

Forgot to reply to all! Forwarded Message Subject: Re: [EXTERNAL] couple of questions on QUIC Interop Date: Tue, 23 May 2023 17:12:26 +0200 From: Frederic Lecaille To: Илья Шипицин On 5/22/23 12:00, Илья Шипицин wrote: > Hello, Hello, > I played with QUIC Interop

Re: Reproducible ERR_QUIC_PROTOCOL_ERROR with all QUIC-enabled versions (2.6 to latest 2.8-dev)

On 4/18/23 17:07, Zakharychev, Bob wrote: > While experimenting with enabling QUIC in HAProxy sitting in front of > our closed-source application I stumbled upon a reproducible QUIC > protocol failure/malfunction while accessing specific CSS resource, > which is served via internal application

Re: [EXTERNAL] Re: HTTP/3 -- POST requests not working

On 4/12/22 22:42, Shawn Heisey wrote: >> Please, you could you double check on your side the "stream" traces are >> correctly enabled? Also ensure you provide use with traces dumped by >> haproxy when you validate the PHP form. > > > These are the trace commands that I am sending to the stats

Re: [EXTERNAL] Re: HTTP/3 -- POST requests not working

Hello Shawn, On 4/12/22 18:30, Shawn Heisey wrote: > On 4/12/22 09:45, Amaury Denoyelle wrote: >> After much analysis of the code, it may be useful to have a run with the >> stream traces as well : >> $ trace stream sink buf0; trace stream level developer; trace stream >> verbosity clean; trace

Re: [EXTERNAL] Re: QUIC and HTTP/3

On 4/10/22 16:09, Shawn Heisey wrote: > On 4/10/2022 3:41 AM, Frederic Lecaille wrote: >> Here is a "bind" line example (SSL must be enable as for TCP) for a >> QUIC/h3 listener: >> >> bind quic4@ ssl crt proto quic alpn h3 > > Frederic is replyin

Re: [EXTERNAL] [PATCH] get BoringSSL back to the game

On 1/31/22 6:22 AM, Илья Шипицин wrote: > Hello, > > 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) supported, but no QUIC > 3) supported for

Re: [ANNOUNCE] haproxy-2.4-dev5

On 1/7/21 11:03 AM, William Dauchy wrote: unclear whether this is on my side only because I did not investigate but I have two tests failing for a while now: ## Starting vtest ## Testing with haproxy version: 2.4-dev5-761d64-4 #top TEST

Re: [PR] Add srvkey option to stick-table

On 12/19/20 9:07 AM, Thayne McCombs wrote: From 731d6a00f3cf0c70d7a8a916e1984c225f3a9dd6 Mon Sep 17 00:00:00 2001 From: Thayne McCombs Date: Sat, 19 Dec 2020 00:59:35 -0700 Subject: [PATCH] Add test for stickiness using the server address for the  server key ---  

Re: [PR] Add srvkey option to stick-table

On 12/16/20 8:39 AM, Thayne McCombs wrote: On 12/10/20 1:31 AM, Frederic Lecaille wrote: It would be preferable to send all your patches, so that others than me may review your work (no diff between different versions of patches) and continue to split your work in several patches. Ok, here

Re: [PR] Add srvkey option to stick-table

On 12/10/20 8:20 AM, Thayne McCombs wrote: Here are my updates from the feedback. It took me quite a while to figure out how to send this diff properly formatted with gmail. If you would like a single patch with all my changes, I can send that as well. About a possible reg test, I remember

Re: [PR] Add srvkey option to stick-table

On 12/10/20 8:20 AM, Thayne McCombs wrote: Here are my updates from the feedback. It took me quite a while to figure out how to send this diff properly formatted with gmail. Thank you for your effort. The result is perfect. If you would like a single patch with all my changes, I can send

Re: [PR] Add srvkey option to stick-table

On 12/2/20 8:48 AM, Thayne McCombs wrote: Thanks for your feedback. I have some followup questions. I think you should initialized this ebtree with EB_ROOT_UNIQUE as value. I'm not sure I understand what the distinction between EB_ROOT and EB_ROOT_UNIQUE is. I'm happy to add this, but I'd

Re: [PR] Add srvkey option to stick-table

On 12/1/20 11:50 AM, Emeric Brun wrote: Hi, Hi Thayne, See my answers below. On 11/30/20 10:23 AM, PR Bot wrote: Dear list! Author: Thayne McCombs Number of patches: 2 This is an automated relay of the Github pull request: Add srvkey option to stick-table Patch title(s): Add

Re: QUIC and the PROXY protocol

On 10/9/20 3:54 PM, William Dauchy wrote: Hi Simon, Hi Simon, On Fri, Oct 9, 2020 at 3:10 PM Simon Ser wrote: The IETF-QUIC transport protocol spec [1] hasn't been ratified, but there exists a number of QUIC deployments in the wild. I'm writing a proxy and I'd like to add support for QUIC.

Re: Segfault with HAProxy 2.0 with peers

On 3/24/20 7:01 PM, William Lallemand wrote: On Tue, Mar 24, 2020 at 05:41:48PM +0100, Olivier D wrote: Hello, With latest haproxy 2.0, you can generate a simple segfault with only configuration test (haproxy -f test.cfg -c) Config content : -- defaults mode http

Re: Peers, logs and debugging.

On 11/5/19 11:06 AM, Frederic Lecaille wrote: On 11/4/19 1:52 PM, Willy Tarreau wrote: Hi Yves, On Mon, Nov 04, 2019 at 10:47:23AM +0100, Yves Lafon wrote: Hi, Trying to debug why some replications are stuck between peers, I was wondering if it was possible to have low-level logging

Re: Peers, logs and debugging.

On 11/4/19 1:52 PM, Willy Tarreau wrote: Hi Yves, On Mon, Nov 04, 2019 at 10:47:23AM +0100, Yves Lafon wrote: Hi, Trying to debug why some replications are stuck between peers, I was wondering if it was possible to have low-level logging of connections or at least TCP states in the peers

Re: HAProxy 2.0 "stick on src table mypeers/mytable" does not result in peers binding to socket address

On 8/31/19 12:20 PM, Willy Tarreau wrote: Hi Bruno, On Sat, Aug 31, 2019 at 12:49:15AM +, Bruno Henc wrote: Greetings, Using "stick on src table mypeers/stickysrc" in a backend results in HAProxy deciding not to bind to the appropriate peers address for the local host (i.e. HAProxy thinks

Re: The server-template and default-server options

On 8/6/19 5:03 AM, Igor Cicimov wrote: Hi all, Hi Igor, Just a quick one to confirm for sure, can/does server-template considers/inherits the options from a default-server line? Yes. The server templates inherits their options from default-server line. Fred.

Re: tfo on default-server settings

On 7/4/19 1:36 PM, Olivier Houchard wrote: Hi William, On Wed, Jul 03, 2019 at 04:52:14PM +, William Dauchy wrote: Hello, On haproxy v2.0.x, while using tfo option in default-server: default-server inter 5s fastinter 1s fall 3 slowstart 20s observe layer7 error-limit 5 on-error

Re: [PATCH 0/9] Fix issues detected by clang analyzer.

On 6/24/19 10:03 AM, Tim Düsterhus wrote: Willy, Am 24.06.19 um 07:33 schrieb Willy Tarreau: Hi Tim, [snipped] If it emits an error when using sizeof(int) instead of sizeof(*foo) where foo is an pointer to unsigned int, it is bogus. I challenge you to present me a relevant architecture

Re: [PATCH 4/9] BUG/MINOR: mworker: Fix segmentation fault during cfgparse

Hi Ilya, On 6/24/19 8:25 AM, Илья Шипицин wrote: I had to be mroe detailed :) I meant "simple reg test" + address sanitizer which we run in travis address sanitizer is capable of catching those things No, we do not write reg test anymore for bugs which have very few chance to come back.

Re: [PATCH 2/9] BUG/MINOR: log: Detect missing sampling ranges in config

On 6/24/19 11:01 AM, Frederic Lecaille wrote: Hi Tim, On 6/23/19 10:10 PM, Tim Duesterhus wrote: Consider a config like: global log 127.0.0.1:10001 sample :10 local0 No sampling ranges are given here, leading to NULL being passed as the first argument to qsort

Re: [PATCH 2/9] BUG/MINOR: log: Detect missing sampling ranges in config

Hi Tim, On 6/23/19 10:10 PM, Tim Duesterhus wrote: Consider a config like: global log 127.0.0.1:10001 sample :10 local0 No sampling ranges are given here, leading to NULL being passed as the first argument to qsort. This configuration does not make sense anyway, a log without

Re: missing table name src_conn_rate

On 6/20/19 1:02 PM, William Dauchy wrote: Hi Fred, On Thu, Jun 20, 2019 at 09:44:51AM +0200, Frederic Lecaille wrote: In fact it seems I have broken something and missed this case. Here is a patch which should fix this issue. Thanks for the patch, it fixes the issue. From

Re: missing table name src_conn_rate

On 6/20/19 12:59 AM, William Dauchy wrote: Hello, Hello William, We are using "rate limiting" config such as the one mentioned below: backend foo stick-table type ip size 200k expire 30s store conn_rate(60s) tcp-request content track-sc1 src http-request deny deny_status 429

Re: VTest output change

On 6/17/19 3:19 PM, Poul-Henning Kamp wrote: Hi, Hi Poul-Henning, For reason now obscured by history, VTest has a (relative) timestamp on every line of its output: *** v1 27.4 CLI RX 300 v1 27.4 CLI RX|Cannot set the active VCL cold. ** v1 27.4 CLI 300

Re: [BUG] memory leak with treads and stick-table/peers

On 6/5/19 3:06 PM, Emmanuel Hocdet wrote: Hi, Hi Emmanuel, After switched to haproxy 1.9 with threads activated, i noticed a significant memory leak. Is valgrind able to expose this memory leak? With threads disable (and bind process omitted) leak disappear. This seems to be related to

Re: reg-tests are broken when running osx + openssl

On 5/6/19 11:25 AM, Frederic Lecaille wrote: On 5/6/19 9:54 AM, Илья Шипицин wrote: there's some random failure https://travis-ci.com/haproxy/haproxy/jobs/197824840 looks like test is not stable According to the log, S13 and S37 syslog servers have the same port: 42464 Obviously

Re: reg-tests are broken when running osx + openssl

On 5/6/19 9:54 AM, Илья Шипицин wrote: there's some random failure https://travis-ci.com/haproxy/haproxy/jobs/197824840 looks like test is not stable According to the log, S13 and S37 syslog servers have the same port: 42464 Fred.

Re: reg-tests are broken when running osx + openssl

On 5/5/19 9:51 AM, Willy Tarreau wrote: On Fri, May 03, 2019 at 07:27:48PM +0200, Frederic Lecaille wrote: - - env VTEST_PROGRAM=../vtest/vtest make reg-tests + - env TMPDIR=~/tmp VTEST_PROGRAM=../vtest/vtest make reg-tests That may sound like a stupid question, but what makes you think

Re: reg-tests are broken when running osx + openssl

On 5/3/19 5:35 PM, Frederic Lecaille wrote: On 5/3/19 3:44 PM, Илья Шипицин wrote: пт, 3 мая 2019 г. в 18:42, Tim Düsterhus <mailto:t...@bastelstu.be>>:     Ilya,     Am 03.05.19 um 15:39 schrieb Илья Шипицин: > when I played with enabling travis-ci, I tried to set TMPDIR

Re: reg-tests are broken when running osx + openssl

On 5/3/19 3:44 PM, Илья Шипицин wrote: пт, 3 мая 2019 г. в 18:42, Tim Düsterhus >: Ilya, Am 03.05.19 um 15:39 schrieb Илья Шипицин: > when I played with enabling travis-ci, I tried to set TMPDIR directly, > however I was not lucky enough.

Re: reg-tests are broken when running osx + openssl

On 5/3/19 1:34 PM, Tim Düsterhus wrote: Fred, Ilya, Hello Tim, Am 03.05.19 um 13:20 schrieb Frederic Lecaille: About the test which fail, I would say that such errors are not negligible :     Starting frontend GLOBAL: cannot change UNIX socket ownership [/var/folders/nz

Re: reg-tests are broken when running osx + openssl

On 5/3/19 1:20 PM, Frederic Lecaille wrote: So on OSX you should try to use/create a temporary working director where you have enough permissions to create a stats UNIX socket with 0600 as permissions. I meant you should try to create a temporary working directory for vtest using the TMPDIR

Re: reg-tests are broken when running osx + openssl

On 5/3/19 11:39 AM, Илья Шипицин wrote: Hello, I'm expanding openssl matrix. here's failing build https://travis-ci.org/chipitsine/haproxy-1/jobs/527683332 Hello Ilya, In fact this has nothing to see with openssl. A lot of tests without any usage of TLS/SSL also fail. There are a lot of

Re: reg-tests fail on FreeBSD 12.0

On 4/30/19 11:24 AM, Илья Шипицин wrote: you are right. let us exclude that particular test from freebsd (what your patch exactly does) Ok Thank you Ilya. Willy could you merge this patch if we decide to disable this reg test on FreeBSD systems. It had already been fixed to make it succeed

Re: reg-tests fail on FreeBSD 12.0

ot;, check duration: [[:digit:]]+ms, status: 0/1 DOWN."  } -start it works, test is green now (on freebsd) https://cirrus-ci.com/task/6252507322908672 пн, 29 апр. 2019 г. в 19:14, Frederic Lecaille <mailto:flecai...@haproxy.com>>: On 4/29/19 3:56 PM, Илья Шипицин wrote

Re: reg-tests fail on FreeBSD 12.0

On 4/29/19 3:56 PM, Илья Шипицин wrote: well, in cirrus-ci we can choose several freebsd images. I just picked up the most recent one. I'll try older images soon. actually, there are several options 1) add special "ignore" to those tests (can we ignore certain tests, for Well this reg

Re: reg-tests fail on FreeBSD 12.0

On 4/29/19 2:18 PM, Frederic Lecaille wrote: On 4/27/19 1:28 AM, Илья Шипицин wrote: please have a look build script: https://github.com/chipitsine/haproxy-1/commit/6739f36463dc9e82eb65a9fa8353a42128403f0c build log (error): https://api.cirrus-ci.com/v1/task/5196617547251712/logs/main.log

Re: reg-tests fail on FreeBSD 12.0

On 4/27/19 1:28 AM, Илья Шипицин wrote: please have a look build script: https://github.com/chipitsine/haproxy-1/commit/6739f36463dc9e82eb65a9fa8353a42128403f0c build log (error): https://api.cirrus-ci.com/v1/task/5196617547251712/logs/main.log any idea ? thanks! Ilya Shipicin Hello

Re: [PATCH] FEATURE/MEDIUM: enable travis-ci builds

On 4/16/19 8:17 PM, Илья Шипицин wrote: + - make CC=$CC V=1 TARGET=$TARGET + - export PATH=${PATH}:${PWD}/VTest + - export VTEST_PROGRAM="VTest/vtest -v" # "VTest/vtest -v" Just to let you note that if you build vtest in the same directory as haproxy ones + - make reg-tests with this

Re: running reg-test when haproxy is built without USE_OPENSSL

On 4/17/19 9:01 AM, Илья Шипицин wrote: Hello, Hi, when playing with travis-ci build matrix, I see that the following tests fail reg-tests/ssl/* if haproxy is built without ssl. also, I've found that lua tests are guarded with #REQUIRE_OPTIONS=LUA should we guard ssl test in the same

vtest update

Hello ML, We have recently modified some reg tests which require an update for vtest, especially these ones: reg-tests/peers/s_basic_sync.vtc (added) reg-tests/peers/s_tls_basic_sync.vtc (added) reg-tests/http-messaging/h0.vtc(modified) So, if some reg tests fail

Re: Compilation fails on OS-X

On 2/14/19 3:12 PM, Patrick Hemmer wrote: On 2019/2/14 08:20, Frederic Lecaille wrote: On 2/14/19 1:32 PM, Frederic Lecaille wrote: On 2/13/19 7:30 PM, Patrick Hemmer wrote: On 2019/2/13 10:29, Olivier Houchard wrote: Hi Patrick, On Wed, Feb 13, 2019 at 10:01:01AM -0500, Patrick Hemmer

Re: Compilation fails on OS-X

On 2/14/19 1:32 PM, Frederic Lecaille wrote: On 2/13/19 7:30 PM, Patrick Hemmer wrote: On 2019/2/13 10:29, Olivier Houchard wrote: Hi Patrick, On Wed, Feb 13, 2019 at 10:01:01AM -0500, Patrick Hemmer wrote: On 2019/2/13 09:40, Aleksandar Lazic wrote: Am 13.02.2019 um 14:45 schrieb Patrick

Re: Compilation fails on OS-X

On 2/13/19 7:30 PM, Patrick Hemmer wrote: On 2019/2/13 10:29, Olivier Houchard wrote: Hi Patrick, On Wed, Feb 13, 2019 at 10:01:01AM -0500, Patrick Hemmer wrote: On 2019/2/13 09:40, Aleksandar Lazic wrote: Am 13.02.2019 um 14:45 schrieb Patrick Hemmer: Trying to compile haproxy on my

Re: reg-tests situation in haproxy 1.8

On 1/19/19 8:53 AM, Willy Tarreau wrote: Hi Lukas, On Fri, Jan 18, 2019 at 12:43:34PM +0100, Lukas Tribus wrote: Hello, currently we have 4 reg-tests in haproxy-1.8, backported due to the actual bugfix commit, which included a test. We also have a broken symbolic link in

Re: reg-tests situation in haproxy 1.8

On 1/19/19 8:53 AM, Willy Tarreau wrote: Hi Lukas, On Fri, Jan 18, 2019 at 12:43:34PM +0100, Lukas Tribus wrote: Hello, currently we have 4 reg-tests in haproxy-1.8, backported due to the actual bugfix commit, which included a test. We also have a broken symbolic link in

Re: [PATCH 10/10] DOC: peers: SSL/TLS documentation for "peers"

On 1/14/19 2:56 PM, Willy Tarreau wrote: Hi Fred, first, thanks for reviving this! On Fri, Jan 11, 2019 at 02:52:24PM +0100, flecai...@haproxy.com wrote: +bind [param*] + Defines the binding parameters of the local peer of this "peers" section. + To avoid some redundancy, and as the and

Re: [PATCH] REG-TEST: mailers: add new test for 'mailers' section

On 1/11/19 12:35 AM, Cyril Bonté wrote: Hi all, Le 08/01/2019 à 10:06, Willy Tarreau a écrit : On Tue, Jan 08, 2019 at 09:31:22AM +0100, Frederic Lecaille wrote: Indeed this script could worked with a short mailer timeout before af4021e6 commit. Another git bisect shows that 53216e7d

Re: [PATCH 1/1] REGTEST: "capture (request|response)" regtest.

On 1/9/19 10:12 AM, Willy Tarreau wrote: On Tue, Jan 08, 2019 at 10:24:16AM +0100, flecai...@haproxy.com wrote: reg-tests/http-capture/h0.vtc | 92 +++ Nice one, thanks Fred, now merged! I'd be careful regarding expectations on log lines about stuff

Re: [RFC PATCH] couple of reg-tests

On 1/9/19 3:22 PM, Jarno Huuskonen wrote: Hello Frederic, On Mon, Jan 07, Frederic Lecaille wrote: reg-tests/http-rules/h3.vtc fails on my side due to a typo in the regex with this error: h10.0 CLI regexp error: 'missing opening brace after \o' (@48) (^0x[a-f0-9]+ example\.org

Re: [PATCH] REGTEST: filters: add compression test

On 1/9/19 10:43 AM, Frederic Lecaille wrote: On 1/8/19 11:25 PM, PiBa-NL wrote: Hi Frederic, Hi Pieter, Op 7-1-2019 om 10:13 schreef Frederic Lecaille: On 12/23/18 11:38 PM, PiBa-NL wrote: As requested hereby the regtest send for inclusion into the git repository. It is OK like

Re: [PATCH] REGTEST: filters: add compression test

On 1/8/19 11:25 PM, PiBa-NL wrote: Hi Frederic, Hi Pieter, Op 7-1-2019 om 10:13 schreef Frederic Lecaille: On 12/23/18 11:38 PM, PiBa-NL wrote: As requested hereby the regtest send for inclusion into the git repository. It is OK like that. Note that you patch do not add reg-test/filters

Re: regtests - with option http-use-htx

On 1/8/19 9:05 PM, PiBa-NL wrote: Hi Frederic, Op 8-1-2019 om 16:27 schreef Frederic Lecaille: On 12/15/18 4:52 PM, PiBa-NL wrote: Hi List, Willy, Trying to run some existing regtests with added option: option http-use-htx Using: HA-Proxy version 1.9-dev10-c11ec4a 2018/12/15 I get

Re: regtests - with option http-use-htx

On 12/15/18 4:52 PM, PiBa-NL wrote: Hi List, Willy, Trying to run some existing regtests with added option: option http-use-htx Using: HA-Proxy version 1.9-dev10-c11ec4a 2018/12/15 I get the below issues sofar: based on /reg-tests/connection/b0.vtc Takes 8 seconds to pass, in a

Re: [PATCH] REG-TEST: mailers: add new test for 'mailers' section

On 1/7/19 9:24 PM, PiBa-NL wrote: Hi Willy, Op 7-1-2019 om 15:25 schreef Willy Tarreau: Hi Pieter, On Sun, Jan 06, 2019 at 04:38:21PM +0100, PiBa-NL wrote: The 23654 mails received for a failed server is a bit much.. I agree. I really don't know much how the mails work to be honest, as I

Re: [RFC PATCH] couple of reg-tests

On 1/2/19 2:17 PM, Jarno Huuskonen wrote: Hello, Hello Jarno, Sorry for this late reply. I started playing with reg-tests and came up with couple of regtests. Is there a better subdirectory for these than http-rules ? Maybe map/b0.vtc and converter/h* ? No, at this time it is ok.

Re: [PATCH] REGTEST: filters: add compression test

On 12/23/18 11:38 PM, PiBa-NL wrote: Added LUA requirement into the test.. Op 23-12-2018 om 23:05 schreef PiBa-NL: Hi Frederic, Hi Pieter, Sorry for this late reply. As requested hereby the regtest send for inclusion into the git repository. Without randomization and with your .diff

Re: corruption of data with compression in 1.9-dev10

On 12/12/18 2:08 AM, PiBa-NL wrote: Hi List, Didn't have time yet to bisect when it went wrong. But attached testfile produces the following output after 3 curl requests at different speeds, this seems to trigger a problem as the hash of the downloaded content is nolonger the same as it

[PATCH] REGTEST: level 1 health-check test 2.

Here is a new reg test for the health-check. Sounds similar to h1.vtc but is more intensive with client connections to verify there is no connection consumption by the health checks. Also checks that only servers with "check" option are "health-check'ed". Fred. From

Re: [PATCH] REGTEST: Add a first test for health-checks.

On 12/11/18 7:18 PM, Frederic Lecaille wrote: On 12/11/18 7:11 PM, Frederic Lecaille wrote: On 12/11/18 11:46 AM, Frederic Lecaille wrote: On 12/11/18 11:29 AM, Frederic Lecaille wrote: On 12/11/18 11:13 AM, Frederic Lecaille wrote: Hi ML, Here is a first reg test for the health-checks. I

Re: [PATCH] REGTEST: Add a first test for health-checks.

On 12/11/18 7:11 PM, Frederic Lecaille wrote: On 12/11/18 11:46 AM, Frederic Lecaille wrote: On 12/11/18 11:29 AM, Frederic Lecaille wrote: On 12/11/18 11:13 AM, Frederic Lecaille wrote: Hi ML, Here is a first reg test for the health-checks. I hope it is as most deterministic as possible

Re: [PATCH] REGTEST: Add a first test for health-checks.

On 12/11/18 11:46 AM, Frederic Lecaille wrote: On 12/11/18 11:29 AM, Frederic Lecaille wrote: On 12/11/18 11:13 AM, Frederic Lecaille wrote: Hi ML, Here is a first reg test for the health-checks. I hope it is as most deterministic as possible. At this time, I did not manage to make it fail

[PATCH] REGTEST: Reg test for "check" health-check option

Here is a new patch for a new reg test (health-check). Fred. From 6d1d882d19c25482d4c2ece7a9baad9452d19c3d Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Fr=C3=A9d=C3=A9ric=20L=C3=A9caille?= Date: Tue, 11 Dec 2018 16:19:34 +0100 Subject: [PATCH] REGTEST: Reg test for "check" health-check option. ---

Re: [PATCH] REGTEST: Add a first test for health-checks.

On 12/11/18 11:29 AM, Frederic Lecaille wrote: On 12/11/18 11:13 AM, Frederic Lecaille wrote: Hi ML, Here is a first reg test for the health-checks. I hope it is as most deterministic as possible. At this time, I did not manage to make it fail (takes ~130ms on my PC). Fred. Well, I have

Re: [PATCH] REGTEST: Add a first test for health-checks.

On 12/11/18 11:13 AM, Frederic Lecaille wrote: Hi ML, Here is a first reg test for the health-checks. I hope it is as most deterministic as possible. At this time, I did not manage to make it fail (takes ~130ms on my PC). Fred. Well, I have not checked the haproxy version required

[PATCH] REGTEST: Add a first test for health-checks.

Hi ML, Here is a first reg test for the health-checks. I hope it is as most deterministic as possible. At this time, I did not manage to make it fail (takes ~130ms on my PC). Fred. varnishtest "Health-check test" feature ignore_unknown_macro # This script test health-checks for four backends

[PATCH] REGTEST: Move LUA reg level 4 test 4 to level 1

Hi all, I think that Pieter level 4 LUA 4 script should be moved to level 1 (as a feature test). Fred. >From ac0188df083da4e240f87c34557cbf0ab9fd589d Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Fr=C3=A9d=C3=A9ric=20L=C3=A9caille?= Date: Fri, 7 Dec 2018 11:16:35 +0100 Subject: [PATCH] REGTEST:

Re: BUG: Lua tasks can't use client sockets after bf89ff3d

On 11/30/18 2:42 AM, PiBa-NL wrote: Hi Frederic, Adis, Hi Pieter, Op 29-11-2018 om 14:53 schreef Frederic Lecaille: Hi Adis, On 11/29/18 10:03 AM, Adis Nezirovic wrote: On Thu, Nov 29, 2018 at 09:03:34AM +0100, Willy Tarreau wrote: OK thanks, I'll take a look at it once I've flushed my

Re: [PATCH] REGTEST/MINOR: script: add run-regtests.sh script

On 11/29/18 10:04 PM, Frederic Lecaille wrote: On 11/29/18 5:36 AM, Willy Tarreau wrote: Hi guys, On Wed, Nov 28, 2018 at 11:17:22AM +0100, Frederic Lecaille wrote: Perhaps we should "chmod +x" this script. Good point, done here. However I'm now seeing this whe

Re: [PATCH] REGTEST/MINOR: script: add run-regtests.sh script

On 11/29/18 5:36 AM, Willy Tarreau wrote: Hi guys, On Wed, Nov 28, 2018 at 11:17:22AM +0100, Frederic Lecaille wrote: Perhaps we should "chmod +x" this script. Good point, done here. However I'm now seeing this when starting it : ## Starting v

Re: [PATCH] REGTEST/MINOR: script: add run-regtests.sh script

On 11/29/18 8:47 AM, Willy Tarreau wrote: On Thu, Nov 29, 2018 at 05:36:35AM +0100, Willy Tarreau wrote: However I'm well aware that it's easier to work on improvements once the script is merged, so what I've done now is to merge it and create a temporary "reg-tests2" target in the makefile to

Re: BUG: Lua tasks can't use client sockets after bf89ff3d

Hi Adis, On 11/29/18 10:03 AM, Adis Nezirovic wrote: On Thu, Nov 29, 2018 at 09:03:34AM +0100, Willy Tarreau wrote: OK thanks, I'll take a look at it once I've flushed my pending stuff on H2+HTX :-( Great, I had my morning coffee and visited my optometrist, so here is a fixed test script

[PATCH] REGTEST: Fix LEVEL 4 script 0 of "connection" module.

Here is a little reg test fix. Fred. >From 61fd6486eee833b42a342993706b656537079242 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Fr=C3=A9d=C3=A9ric=20L=C3=A9caille?= Date: Thu, 29 Nov 2018 14:23:32 +0100 Subject: [PATCH] REGTEST: Fix LEVEL 4 script 0 of "connection" module. Prevent this script

[PATCH] REGTEST: Add a basic test for the cache.

Here is a little patch for a basic test for the cache. Fred. >From aa301c6eef5c6797283d56b9f23266345808cd1e Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Fr=C3=A9d=C3=A9ric=20L=C3=A9caille?= Date: Wed, 28 Nov 2018 11:36:48 +0100 Subject: [PATCH] REGTEST: Add a basic test for the cache. The client

Re: [PATCH] REGTEST/MINOR: script: add run-regtests.sh script

On 11/27/18 11:17 PM, PiBa-NL wrote: Hi Frederic, Willy, Op 27-11-2018 om 15:00 schreef Frederic Lecaille: On 11/27/18 10:44 AM, Frederic Lecaille wrote: On 11/27/18 9:52 AM, Willy Tarreau wrote: Hi guys, On Tue, Nov 27, 2018 at 09:45:25AM +0100, Frederic Lecaille wrote: I put the script

Re: [PATCH] REGTEST/MINOR: script: add run-regtests.sh script

On 11/27/18 10:44 AM, Frederic Lecaille wrote: On 11/27/18 9:52 AM, Willy Tarreau wrote: Hi guys, On Tue, Nov 27, 2018 at 09:45:25AM +0100, Frederic Lecaille wrote: I put the script in the /reg-tests/ folder. Maybe it should have been besides the Makefile in the / root ? Yes I think

Re: [PATCH] REGTEST/MINOR: script: add run-regtests.sh script

On 11/27/18 9:52 AM, Willy Tarreau wrote: Hi guys, On Tue, Nov 27, 2018 at 09:45:25AM +0100, Frederic Lecaille wrote: I put the script in the /reg-tests/ folder. Maybe it should have been besides the Makefile in the / root ? Yes I think it should be placed at the same level as the Makefile

Re: [PATCH] REGTEST/MINOR: script: add run-regtests.sh script

On 11/25/18 4:59 PM, PiBa-NL wrote: Hi Frederic, Willy, Hi Pieter, Added the varnishtest script we have been discussing as a .patch this time. I put the script in the /reg-tests/ folder. Maybe it should have been besides the Makefile in the / root ? Yes I think it should be placed at the

Re: reg-test failures on FreeBSD, how to best adapt/skip some tests?

On 11/23/18 1:12 AM, PiBa-NL wrote: Hi Frederic, Hi Pieter, I still have a ' ' newline, with the IFS= but the \n and \012 didnt seem to work there.. Strangely on my PC with both bash and dash I do not have to change IFS value to parse HAPROXY_VERSION, TARGET and OPTIONS with "read"

Re: reg-test failures on FreeBSD, how to best adapt/skip some tests?

On 11/19/18 10:08 PM, PiBa-NL wrote: Hi Frederic, Willy, Hi Pieter, Thank you a lot again for this work Pieter. Hello Pieter, Do you intend to finalize this script? We would like to use it in haproxy sources. Note that varnishtest already uses TMPDIR variable in place of /tmp if it is

Re: varnishtest with H2>HTX>H1(keep-alive)

On 11/19/18 8:10 PM, PiBa-NL wrote: Hi Willy, Op 19-11-2018 om 4:37 schreef Willy Tarreau: Hi Pieter, On Mon, Nov 19, 2018 at 01:07:44AM +0100, PiBa-NL wrote: Hi List, I'm trying (and failing?) to write a H2>HTX>H1(keepalive) test. Using haproxy 1.9-dev6-05b9b64. Test vtc attached, i

Re: varnishtest with H2>HTX>H1(keep-alive)

On 11/19/18 1:07 AM, PiBa-NL wrote: Hi List, Hi Pieter, Christopher is CC'ed. As your mail is about reg-testing I took a look at it. I'm trying (and failing?) to write a H2>HTX>H1(keepalive) test. Using haproxy 1.9-dev6-05b9b64. Test vtc attached, i added the 'option http-use-htx' to the

Re: reg-test failures on FreeBSD, how to best adapt/skip some tests?

On 11/8/18 6:11 AM, Willy Tarreau wrote: Hi guys, On Wed, Nov 07, 2018 at 09:37:14AM +0100, Frederic Lecaille wrote: New 'version' of the script attached. It now supports a set of parameters to modify its behavior a little. And also checking for a 'version requirement'. So a H2 test doesn't

Re: reg-test failures on FreeBSD, how to best adapt/skip some tests?

On 11/8/18 6:11 AM, Willy Tarreau wrote: Hi guys, On Wed, Nov 07, 2018 at 09:37:14AM +0100, Frederic Lecaille wrote: New 'version' of the script attached. It now supports a set of parameters to modify its behavior a little. And also checking for a 'version requirement'. So a H2 test doesn't

Re: [PATCH] HTTP 103 response (Early Hints)

On 11/13/18 7:48 AM, Aleksandar Lazic wrote: Hi Fred. Hello Aleksandar, Sorry to be picky but I still think that there is some missing text in the documentation, as mentioned before. http://git.haproxy.org/?p=haproxy.git;a=commitdiff;h=06f5b6435ba99b7a6a034d27b56192e16249f6f0 MINOR: doc: 

Re: reg-test failures on FreeBSD, how to best adapt/skip some tests?

On 10/28/18 8:01 PM, PiBa-NL wrote: Hi Frederic, Hello Pieter, Sorry again for this late reply. Op 19-10-2018 om 11:51 schreef Frederic Lecaille: The idea of the script sounds good to me. About the script itself it is a nice work which could be a good start. Thanks. Just a few details

Re: [PATCH] MINOR: cache: Add "Age" header.

On 10/26/2018 02:52 PM, Frederic Lecaille wrote: Hello, Here is a patch to handle the "Age" header for the cache. Everything is in the commit log. Here is a better patch with this diff between this latter one and the previous one: @@ -52,7 +52,7 @@ + age = 0; + c

[PATCH] MINOR: cache: Add "Age" header.

Hello, Here is a patch to handle the "Age" header for the cache. Everything is in the commit log. Regards, Fred. >From af5156e33de0a5a2f278cd6b8834e834c5401b35 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Fr=C3=A9d=C3=A9ric=20L=C3=A9caille?= Date: Fri, 26 Oct 2018 14:29:22 +0200 Subject: [PATCH]

Re: [PATCHES] Cache for larger HTTP objects

On 10/25/2018 07:01 PM, William Lallemand wrote: Hi Fred! On Thu, Oct 25, 2018 at 10:59:43AM +0200, Frederic Lecaille wrote: Well, after having checked, haproxy could start with a cache bigger than 2047 MB on my PC due to parsing issue. I provide three patches. The first fixes the "tota

  1   2   3   >