Hi Christopher,
Op 29-5-2020 om 09:00 schreef Christopher Faulet:
Le 29/05/2020 à 00:45, PiBa-NL a écrit :
Hi List,
I noticed a issue with 2.2-dev8-release and with 2.2-dev8-7867525 the
issue is still there that when a reload is 'requested' it fails to stop
the old worker..
Hi Pieter,
I
and provide :).
Regards,
PiBa-NL (Pieter)
*Reproduction (works 99% of the time..):*
haproxy -W -f /var/etc/haproxy-2020/haproxy.cfg
kill -s USR2 17683
*haproxy.cfg*
frontend www
bind 127.0.0.1:81
mode http
backend testVPS_ipv4
mode http
retries
how we can skip such tests ?
I think the test or code should get fixed.. not skipped because it fails.
Note that this specific test recently got this extra 'addr ::1' server
check parameter on srv3. Perhaps that that syntax is written/parsed wrongly?
Cheers,
Ilya Shipitcin
Regards, PiBa-NL
anks and regards,
PiBa-NL (Pieter)
to be
expected for most setups.?.
Not sure if its a bug or a feature request, but i do think it should be
changed :). Can it be added to some todo list? Thanks.
Thanks and regards,
PiBa-NL (Pieter)
for this one.
Question though, are you still working on making a non-existing server
template go into 'resolution' state?
See below/attached picture with some details.. (or see
https://www.mail-archive.com/haproxy@formilux.org/msg36373.html )
Regards,
PiBa-NL (Pieter)
Hi Olivier, Willy,
Just to confirm, as expected it (c3500c3) indeed works for me :).
Thanks for the quick fix!
Regards,
PiBa-NL (Pieter)
Op 25-3-2020 om 17:16 schreef Willy Tarreau:
On Wed, Mar 25, 2020 at 05:08:03PM +0100, Olivier Houchard wrote:
That is... interesting, not sure I reached
have an idea where to look. Providing captures/logs is a bit
difficult without some careful scrubbing..
Regards,
PiBa-NL (Pieter)
### Complete config (that still reproduces the issue.. things cant get
much simpler than this..):
frontend InternalSites.8.6-merged
bind 192.168.8.67
guys,
Thx Tim for investigating.
I'll check the PCAP and see why such behavior happens.
Baptiste
On Tue, Feb 18, 2020 at 12:09 AM Tim Düsterhus mailto:t...@bastelstu.be>> wrote:
Pieter,
Am 09.02.20 um 15:35 schrieb PiBa-NL:
> Before commit '2
in
behaviour)..)
Anyhow the current '2.2-dev2-a71667c, released 2020/02/17' is still
affected.
If someone was already planning to, please don't feel 'pushed' by this
mail. i'm just trying to make sure this doesn't fall through the cracks :).
Regards,
PiBa-NL (Pieter)
Op 9-2-2020 om 15:35 schreef
it
will be kinda 'slow' if it needs to test for hold valid timings..
Regards,
PiBa-NL (Pieter)
haproxy config:
resolvers globalresolvers
nameserver pfs_routerbox 192.168.0.18:53
resolve_retries 3
timeout retry 200
hold valid 3m
hold nx 10s
hold other 15s
hold refused
Hi Olivier,
Just to let you know, seems this commit has broken a few regtests:
http://git.haproxy.org/?p=haproxy.git;a=commit;h=477902bd2e8c1e978ad43d22dba1f28525bb797a
https://api.cirrus-ci.com/v1/task/5885732300521472/logs/main.log
Testing with haproxy version: 2.2-dev1
#top TEST
Houchard:
Hi guys,
On Tue, Jan 14, 2020 at 09:45:34PM +0100, Willy Tarreau wrote:
Hi guys,
On Tue, Jan 14, 2020 at 08:02:51PM +0100, PiBa-NL wrote:
Below a part of the output that the test generates for me. The first curl
request seems to succeed, but the second one runs into a timeout..
When
nly higher with many cores..
* Using commit 0eae632 it works OK*
Just to be sure i re-tested on 16 cores with 2.2-dev0-0eae632 but that
does nicely pass: 0 tests failed, 0 tests skipped, 20 tests passed
Regards,
PiBa-NL (Pieter)
.. Do you (Willy or anyone), need
more information from my side? Or is there a patch i can try to validate?
Regards,
PiBa-NL (Pieter)
Yes im running a somewhat outdated OS here:
FreeBSD freebsd11 11.1-RELEASE FreeBSD 11.1-RELEASE #0 r321309: Fri
Jul 21 02:08:28 UTC 2017
r...@releng2.nyi.free
Op 15-10-2019 om 13:52 schreef William Lallemand:
I pushed the fix.
Thanks
Fix confirmed. Thank you.
Hi Christopher,
It seems you fixed/changed the issue i noticed below a few minutes ago
in commit 452e578 :) , thanks.
One question remaining about this on my side is if it is expected that
some platforms will use 'normalized' URI and others platforms just the
regular / ?
Regards, PiBa-NL
take a look? Thanks in advance.
Regards,
PiBa-NL (Pieter)
sing accolades around the IPv6 address.. not
sure if all machines would use ipv6 for their localhost connection..)
Regards,
PiBa-NL (Pieter)
Hi Willy,
Op 1-8-2019 om 6:21 schreef Willy Tarreau:
Hi Pieter,
On Wed, Jul 31, 2019 at 10:56:54PM +0200, PiBa-NL wrote:
Hi List,
I have build haproxy 2.0.3-0ff395c from sources however after running a
'haproxy -v' it shows up as: 'HA-Proxy version 2.0.3 2019/07/23 -
https://haproxy.org
by the contents of the
repository, can it be changed? I find it really useful to see which
commit a certain compiled haproxy binary was based upon. Thanks in
advance .
Regards,
PiBa-NL (Pieter)
by the contents of the
repository, can it be changed? I find it really useful to see which
commit a certain compiled haproxy binary was based upon. Thanks in
advance :).
Regards,
PiBa-NL (Pieter)
the really short timeouts in the testcase itself
this is an excellent result.
I'm considering this one fully fixed, thanks again.
Regards,
PiBa-NL (Pieter)
Hi Willy,
Op 10-6-2019 om 16:14 schreef Willy Tarreau:
Hi Pieter,
On Mon, Jun 10, 2019 at 04:06:13PM +0200, PiBa-NL wrote:
Things certainly look better again now regarding this issue.
Ah cool!
Running the test repeatedly, and manually looking over the results its
pretty much as good
Hi Willy,
Op 10-6-2019 om 11:09 schreef Willy Tarreau:
Hi Pieter,
On Sat, Jun 08, 2019 at 06:07:09AM +0200, Willy Tarreau wrote:
Hi Pieter,
On Fri, Jun 07, 2019 at 11:32:18PM +0200, PiBa-NL wrote:
Hi Willy,
After the commit "6ec902a MINOR: threads: serialize threads initialization&quo
the 20ms connect/server timeouts to also to fail the test fairly often
but not always..
Seems like something isn't quite right there. Can you check?
Regards,
PiBa-NL (Pieter)
Log can be seen below (p.s. i added milliseconds output also to the
vtest log.. ):
*** h2 0.299 debug|[WARNING]
,
PiBa-NL (Pieter)
Hi Olivier,
Op 6-6-2019 om 18:20 schreef Olivier Houchard:
Hi Pieter,
On Wed, Jun 05, 2019 at 09:00:22PM +0200, PiBa-NL wrote:
Hi Olivier,
It seems this commit ea8dd94 broke something for my FreeBSD11 system.
Before that commit (almost) all vtest's succeed. After it several cause
core-dumps
are the following:
- gdb# bt full of one of the crashed tests..
- summary of failed tests
Regards,
PiBa-NL (Pieter)
gdb --core
/tmp/haregtests-2019-06-05_20-40-20.7ZSvbo/vtc.65353.510907b0/h1/haproxy.core
./work/haproxy-ea8dd94/haproxy
GNU gdb 6.1.1 [FreeBSD]
Copyright 2004 Free Software Foundation, Inc
a
request and when the server will start to have trouble the current
10/minute might be perfectly fine.. or make it a 16666 per 10 seconds.?.
So to sum things up.. the limiting is working, and its allowing 10
request in the first minute, just as specified. So in that regard its
working correctly already..
Regards,
PiBa-NL (Pieter)
-resolving a dns name for the addr setting
as well ?
Regards,
PiBa-NL (Pieter)
Op 21-3-2019 om 20:37 schreef Daniel Schneller:
Hi!
Thanks for the response. I had looked at the "hold" directives, but since they
all seem to have reasonable defaults, I did not touch them.
I spe
RATION:2
]=]
print("Result:\n"..result)
Result:
#EXTM3U
#EXT-X-VERSION:3
#EXT-X-MEDIA-SEQUENCE:01234
#EXT-X-TARGETDURATION:2
Thanks,
Thomas
Am 15.03.2019 um 00:27 schrieb PiBa-NL:
Hi Thomas,
Op 14-3-2019 om 20:28 schreef Thomas Schmiedl:
Hello,
I never got a reply from the o
to include in
haproxy. Thanks
I personally think this is ugly compared to trying to fix the faulty
client. Maybe you can report your issue to the author(s) and share your
config to help them reproduce it ?
Regards,
Willy
Regards,
PiBa-NL (Pieter)
=b8d2ee040aa21f2906a4921e5e1c7afefb7e
I 'think' the syslog output for a single request/response should remain
the same with/without htx? Or should the size check be less strict or
accept 1 of 2 possible outcomes with/without htx.?
Regards,
PiBa-NL (Pieter)
S 0.0 syslog|<134>Feb 26 20:42:52 haproxy[56313
Hi Willy,
Op 2-2-2019 om 0:01 schreef Willy Tarreau:
On Fri, Feb 01, 2019 at 09:43:13PM +0100, PiBa-NL wrote:
The 'last' part is in TCP mode, and is intended like that to allow me to run
tcpdump/wireshark on the un-encrypted traffic, and being certain that
haproxy would not modify it before
Hi Willy, List,
Just a little check, was below mail received properly with the 6
attachments (vtc/vtc/log/png/png/pcapng) .?
(As it didn't show up on the mail-archive.)
Regards,
PiBa-NL (Pieter)
Op 26-1-2019 om 21:04 schreef PiBa-NL:
Hi Willy,
Op 25-1-2019 om 17:04 schreef Willy Tarreau
oblem, but it seems suspicious to me..
Regards,
PiBa-NL (Pieter)
varnishtest "Check H1 client to H2 server with HTX."
feature ignore_unknown_macro
syslog Slog_1 -repeat 1 -level info {
recv
} -start
server s1 -repeat 2 {
rxpri
stream 0 {
txsettings
rxsettings
tx
ertain configuration circumstances existed
for years before it was spotted with the regtest.
https://www.mail-archive.com/haproxy@formilux.org/msg32190.html
http://git.haproxy.org/?p=haproxy.git;a=commit;h=774c486cece942570b6a9d16afe236a16ee12079
Regards,
PiBa-NL (Pieter)
with this patch. Without needing the
'timeout mail' setting.
I think we can call it fixed once committed.
Thanks,
PiBa-NL (Pieter)
om 11:17 schreef Christopher Faulet:
If it's ok for you, I'll also merge your regtest.
Can you add the regtest as well into the git repo?
Regards,
PiBa-NL (Pieter)
Hi Christopher,
Op 14-1-2019 om 11:17 schreef Christopher Faulet:
Le 12/01/2019 à 23:23, PiBa-NL a écrit :
Hi List,
I've configured haproxy with htx and when i try to filter the stats
webpage.
Sending this request: "GET /?;csv;scope=b1" to '2.0-dev0-762475e
2019/01/10' it
**
* VU XUAN HOC
Regards,
PiBa-NL (Pieter)
A regtest is attached that reproduces the behavior, and which i think
could be included into the haproxy repository.
Regards,
PiBa-NL (Pieter)
Program terminated with signal SIGSEGV, Segmentation fault.
#0 0x00564fe7 in strnistr (str1=0x802631048 "fe1", len_str1=3,
str2=0x804
out to
test has a health-check with a 60 second interval..) Anyhow its been
like this for years afaik, i guess it wont matter much if stays like
this a bit longer.
Regards,
PiBa-NL (Pieter)
needs a bit more tweaking.
Regards,
PiBa-NL (Pieter)
Core was generated by `haproxy -d -f /tmp/vtc.37274.4b8a1a3a/h1/cfg'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0 0x00500955 in chk_report_conn_err (check=0x802616a10,
errno_bck=0, expired=1) at src/checks.c:689
689
thread also to aid developers in
reproducing the issue and validating a possible fix.
@Olivier, Willy, may i assume this mailbomb feature is 'planned' to get
fixed in 1.9.2 ? (perhaps a bugtracker with a 'target version' would be
nice ;) ?)
Regards,
PiBa-NL (Pieter)
Thank you Christopher & Frederic.
Op 9-1-2019 om 14:47 schreef Christopher Faulet:
Le 09/01/2019 à 10:43, Frederic Lecaille a écrit :
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 w
if something strange happens again. Might take a few days though, IF it
still occurs..
Regards,
PiBa-NL (Pieter)
Core was generated by `/usr/local/sbin/haproxy -f
/var/etc/haproxy/haproxy.cfg -p /var/run/haproxy.pid'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0 0x004b91c7
Hi Frederic,
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/common.pem which could
be a symlink to ../ssl
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 the below issues sofar:
based
Hi Christopher,
Op 7-1-2019 om 16:32 schreef Christopher Faulet:
Le 06/01/2019 à 16:22, PiBa-NL a écrit :
Hi List,
Using both 1.9.0 and 2.0-dev0-909b9d8 compression happens twice when
configured in defaults.
This was noticed by user walle303 on IRC.
Seems like a bug to me as 1.8.14 does
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 have never used them. I remember
forgotten about :).
The 23654 mails received for a failed server is a bit much..
c2 7.5 EXPECT resp.http.mailsreceived (23654) == "16" failed
Regards,
PiBa-NL (Pieter)
Op 23-12-2018 om 23:37 schreef PiBa-NL:
Changed subject of patch requirement to 'REGTEST'.
Op 23-12-201
in advance.
Regards,
PiBa-NL (Pieter)
s1 0.0
txresp|!"#$%&'()*+,-./0123456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ[\]^_
s1 0.0 txresp|"#$%&'()*+,-./0123456789:;<=>?@ABCD
*** s1 0.0 shutting fd 4
** s1 0.0 Ending
*** h1 0.0 debug|:
Hi Christopher, Willy,
Op 2-1-2019 om 15:37 schreef Christopher Faulet:
Le 29/12/2018 à 01:29, PiBa-NL a écrit :
compression with htx, and a slightly delayed body content it will
prefix some rubbish and corrupt the gzip header..
Hi Pieter,
In fact, It is not a bug related to the compression
c1 0.1 === expect resp.http.content-encoding == "gzip"
c1 0.1 EXPECT resp.http.content-encoding (gzip) == "gzip" match
** c1 0.1 === gunzip
c1 0.1 Gunzip error: Body lacks gzip magics
Can someone take a look? Thanks in advance.
Regards,
PiBa-NL (Pieter)
Changed subject of patch requirement to 'REGTEST'.
Op 23-12-2018 om 21:17 schreef PiBa-NL:
Hi List,
Attached a new test to verify that the 'mailers' section is working
properly.
Currently with 1.9 the mailers sends thousands of mails for my setup...
As the test is rather slow i have marked
be bigger? As you mentioned
needing a 10MB output to reproduce the original issue on your machine?
Regards,
PiBa-NL (Pieter)
From 64460dfeacef3d04af4243396007a606c2e5dbf7 Mon Sep 17 00:00:00 2001
From: PiBa-NL
Date: Sun, 23 Dec 2018 21:21:51 +0100
Subject: [PATCH] REGTEST: filters: add compression
/basic_connection.vtc FAILED (120.236) signal=9
Please can you take a look :) Thanks in advance.
Regards,
PiBa-NL (Pieter)
# Checks a simple request
varnishtest "Checks a simple request"
feature ignore_unknown_macro
server s1 {
rxreq
txresp -bodylen 42202
} -start
haproxy h1 -conf {
global
Hi Christopher,
Fix confirmed.
top 2.5 shell_out|File1 all OK
top 2.5 shell_out|File2 all OK
top 2.5 shell_out|File3 all OK
Thank you!
Regards,
PiBa-NL (Pieter)
Hi Willy,
Op 15-12-2018 om 17:06 schreef Willy Tarreau:
Hi Pieter,
On Sat, Dec 15, 2018 at 04:52:10PM +0100, 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
ize:1024,
used:(0|1\n0x[0-9a-f]*: key=127\.0\.0\.1 use=0 exp=[0-9]* gpt0=0 gpc0=0
gpc0_rate\(1\)=0 conn_rate\(1\)=1 http_req_cnt=1
http_req_rate\(1\)=1 http_err_cnt=0 http_err_rate\(1\)=0)\n$"
Regards,
PiBa-NL (Pieter)
#commit b406b87
# BUG/MEDIUM: connection: don't store
d the .vtc file still
produces files with different hashes for the 3 curl commands for me.
Besides that and as usual thanks for your elaborate response on all the
other subjects :).
Regards,
PiBa-NL (Pieter)
, while shortly before release i would expect mostly little
fixes to issues to get committed. That 'new' features arn't 100% stable,
that might not be a blocker. But existing features that used to work
properly should imho not get released in a broken state..
my 2 cent.
Regards,
PiBa-NL (Pieter)
operation on non-socket
(errno=38), which apparently modifies the syslog behavior.?
Tested with version 1.9-dev10-6e0d8ae, but i think it never worked since
stdout logging was introduced.
Regards,
PiBa-NL (Pieter)
# commit d02286d
# BUG/MINOR: log: pin the front connection when front ip/ports
Hi List, Willy,
Current 1.9-dev master ( 6e0d8ae ) crashes with regtest:
/reg-tests/connection/h1.vtc stack below, it fails after commit f157384.
Can someone check? Thanks.
Regards,
PiBa-NL (Pieter)
Program terminated with signal 11, Segmentation fault.
#0 0x0057f34f
..)
Regards,
PiBa-NL (Pieter)
Copyright 2000-2018 Willy Tarreau
Can anyone confirm? Or perhaps even fix ;) Ill try and dig a little more
tomorrow evening :).
Thanks in advance,
PiBa-NL (Pieter)
local data = "abcdefghijklmnopqrstuvwxyz"
local responseblob = ""
math.randomseed(1)
for i = 1,1 do
Regards,
PiBa-NL (Pieter)
) thought, is there a bug somewhere as the
tcp-health-check 'should' abort the connection even before the
3way-tcp-handshake is completed? And as such s1 should not see that
first connection?? (Is that also possible/valid for a FreeBSD system? Or
would that be a linux trick?)
Regards,
PiBa-NL
on
FreeBSD currently.. I can re-spin the patch with all non-linux targets
listed if desired.
# expose-fd is available starting at version 1.8
#REQUIRE_VERSION=1.8
# abns@ sockets are not available on freebsd
#EXCLUDE_TARGETS=freebsd
Regards,
PiBa-NL (Pieter)
From
nflicting', as the '-bodylen' generates a kinda random
body content. While '-body' defines the exact string to send as a body..
Seems to me that the bodylen should be removed? Patch that does that
attached.
Regards,
PiBa-NL
From e786be564e7dca1e3b347b6cc9e0af05c85e975b Mon Sep 17 00:00:00 2001
Hi Willy,
Op 3-12-2018 om 4:29 schreef Willy Tarreau:
Hi Pieter,
On Mon, Dec 03, 2018 at 12:30:37AM +0100, PiBa-NL wrote:
Hi List,
When running regtest /connection/b0.vtc with the added setting below:
defaults
option http-use-htx
The test no longer completes successfully
isn't emitted at the same 'expected' time?
Regards,
PiBa-NL (Pieter)
] 334/200950 (30141) : Proxy 'test': unable
to find the cache 'my_cache' referenced by the filter 'cache'.
*** h1 0.0 debug|[ALERT] 334/200950 (30141) : Fatal errors found in
configuration.
Can you take a look? Thanks in advance :).
Regards,
PiBa-NL (Pieter)
be back-ported until haproxy 1.6.
It does fail on the current 1.9-dev8-51e01b5 version, and back until
1.9-dev5-3e1f68b .
Hope its okay like this :).
Regards,
PiBa-NL (Pieter)
From 29b2e82eb8461a2994841ba5460583c8acf5cddc Mon Sep 17 00:00:00 2001
From: PiBa-NL
Date: Fri, 30 Nov 2018 21:01:01
of it for inclusion in git? Or can you guys do
that once the fix is also ready.? i think it was the preferred to get
bugfix+regtest 'linked' then ?
Regards,
PiBa-NL (Pieter)
varnishtest "Lua: txn:get_priv() scope"
feature ignore_unknown_macro
#REQUIRE_OPTIONS=LUA
#REQUIRE_VERSION=1.6
server s1 {
188 (http/HTTP)
** Slog_1 0.0 === expect ~ "Connect from .* to
${h1_ssl_addr}:${h1_ssl_port}"
Do you see the same? Is more info needed?
Thanks in advance :)
Regards,
PiBa-NL (Pieter)
t this moment, thank you! (i
suppose your turnaround time from issue>fix will also be shorter than
waiting for my spare evening hour..)
Ill start checking some requirements of existing .vtc . And perhaps
writing new one's.
Regards,
PiBa-NL (Pieter)
akefile to call the ./scripts/run-regtests.sh
Please can someone check it again before merging.?. Thanks guys :).
Regards,
PiBa-NL (Pieter)
From 989bf7ccbfd849deed450291121cdcc68796ba64 Mon Sep 17 00:00:00 2001
From: PiBa-NL
Date: Tue, 27 Nov 2018 22:26:38 +0100
Subject: [PATCH] REGTEST/MINOR: scri
free to comment on them or
change them as required.
Once this one is 'accepted' ill create a few patches for the existing
.vtc files to include their requirements. (at least the more obvious ones..)
Regards,
PiBa-NL (Pieter)
From 4432c10a0a822619c152aa187f18b2f6478ac565 Mon Sep 17 00:00:00
HAPROY_PROGRAM I get this output with a script
with a successful result.
Checks added to avoid this issue for both haproxy and varnishtest so
they are checked to exist.
Next round :).
Regards,
PiBa-NL (Pieter)
#!/usr/bin/env sh
if [ "$1" = "--help" ]; then
cat <
led in logger #2: Socket operation on non-socket (errno=38)
Partial config:
global
log stdout format raw daemon
log :1514 local0
I'm using "HA-Proxy version 1.9-dev7-7ff4f14 2018/11/20" this time.
Or is it (again) something i'm configuring wrongly ? ;) .
Regards,
PiBa-NL (
suggestions. Lemme know if/what i missed :)
Regards,
PiBa-NL (Pieter)
#!/usr/bin/env sh
if [ "$1" == "--help" ]; then
cat << EOF
### run-regtests.sh ###
Running run-regtests.sh --help shows this information about how to use it
Run without parameters to run all t
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 added the 'option http-u
second connection. (the 'old' way..)
Thanks in advance.
Regards
PiBa-NL (Pieter)
** c4 0.2 === txreq -req GET -url /3
*** c4 0.2 tx: stream: 1, type: HEADERS (1), flags: 0x05, size: 37
** c4 0.2 === rxresp
*** h1 0.2 debug|0007:fe4.accept(000e)=0011 from [::1:25432]
ALPN=
*
with SIGTERM
Yes i'm using -W in the varnishtest, and yes that adds a 1 second delay
or something, but that never prevented this test from succeeding for me
before..
Can you take a look?
Regards,
PiBa-NL (Pieter)
Op 6-11-2018 om 18:33 schreef Willy Tarreau:
On Tue, Nov 06, 2018 at 05:37
Hi Lukas,
Op 29-10-2018 om 16:39 schreef Lukas Tribus:
Hi,
On Sun, 28 Oct 2018 at 23:47, PiBa-NL wrote:
Hi List,
When i enable H2 'alpn h2,http/1.1' on haproxy bind line with offloading
'mode http'. The overall loading of a web-application i use takes longer
than without. (Tried with 1.9
0.2 HTTP rx failed (fd:10 read: Connection reset by
peer)" while that is where the s4 server expects a second request over
its keep-alive connection. (assuming i wrote the test correctly..) While
it 'should' fail on the s3 server.
Regards,
PiBa-NL (Pieter)
# h2 with h1 backend connec
Hi Willy,
Op 28-10-2018 om 20:21 schreef Willy Tarreau:
Hi Pieter,
On Sun, Oct 28, 2018 at 12:49:44AM +0200, PiBa-NL wrote:
Hello Chad, List,
Thanks for the nice article
https://www.haproxy.com/blog/introduction-to-haproxy-acls/
However one of the examples that shows how to use cache-store
ded/changed about it before considering to add
it to haproxy sources branch?
Regards,
PiBa-NL (Pieter)
#!/usr/bin/env sh
if [ "$1" == "--help" ]; then
cat << EOF
### run-regtests.sh ###
Running run-regtests.sh --help shows this information about how to use it
(and perhaps include the
cache section declaration also), and perhaps investigate why haproxy
does seem to try and process the fetch it warns about on startup that it
would/should never match..
Regards,
PiBa-NL (Pieter)
# Checks that basic cache is working
varnishtest "Checks that basic
Hi Frederic,
Do you have a little time to take a look at (the idea of) the script?
Thanks in advance :).
Op 3-10-2018 om 21:52 schreef PiBa-NL:
Hi Frederic,
Made a little script (attached)..
What do you think ? Could this work for current 'requirements'?
Regards,
PiBa-NL (Pieter)
ruled out, the 3rd is your only option.. (that i know of
anyhow..)
Regards,
PiBa-NL (Pieter)
Hi William,
Op 12-10-2018 om 10:53 schreef William Lallemand:
The attached patch should fix the issue.
The patch works for me, thanks.
Regards,
PiBa-NL (Pieter)
if i understand correctly. Which eventually
doesn't happen, but is counted. Maybe that is a point that can be
improved in a future version if time permits.? Or would it even be
expected to behave like that?
Regards,
PiBa-NL (Pieter)
code? Get some kind of trace? Anything in
particular that would be of interest?
Regards,
PiBa-NL (Pieter)
Hi Frederic, Willy,
Attached a patch that will change /reg-tests/connection/b0.vtc to
use unix@ sockets so it is compatible with FreeBSD and possibly other OS's.
As discussed in the other thread
https://www.mail-archive.com/haproxy@formilux.org/msg31370.html.
Regards,
PiBa-NL (Pieter
Hi Frederic,
Op 1-10-2018 om 15:15 schreef Frederic Lecaille:
On 09/15/2018 02:03 AM, PiBa-NL wrote:
Hi List, Willy,
Hi Pieter,
Sorry for this late reply.
I am also sorry to tell you that -D option should not be used anymore
because it as been recently broken. It adds an extra 2s delay
Hi Willy,
Op 1-10-2018 om 4:00 schreef Willy Tarreau:
On Sun, Sep 30, 2018 at 10:16:55PM +0200, PiBa-NL wrote:
Hi Willy,
Op 30-9-2018 om 20:38 schreef Willy Tarreau:
On Sun, Sep 30, 2018 at 08:22:23PM +0200, Willy Tarreau wrote:
On Sun, Sep 30, 2018 at 07:59:34PM +0200, PiBa-NL wrote
1 - 100 of 342 matches
Mail list logo