Added LUA requirement into the test..
Op 23-12-2018 om 23:05 schreef PiBa-NL:
Hi Frederic,
As requested hereby the regtest send for inclusion into the git
repository. Without randomization and with your .diff applied. Also
outputting expected and actual checksum if the test fails so its clear
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 i
Hi Frederic,
As requested hereby the regtest send for inclusion into the git
repository. Without randomization and with your .diff applied. Also
outputting expected and actual checksum if the test fails so its clear
that that is the issue detected.
Is it okay like this? Should the blob be bi
Hi,
The attached patch adds the ssl_sni_check converter which returns true
if the sample input string matches a loaded certificate's CN/SAN.
This can be useful to check for example if a host header matches a
loaded certificate CN/SAN before doing a redirect:
frontent fe_main
bind 127.0.0.1:80
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 it with a starting letter 's'.
Note that the test also fails on 1.6/1.7/1.8 but can be 'fixed
Hey Patrick,
Have you looked at the fixes in 1.8.16? They sound kinda-sorta related to
your problem ...
J
On Sun, 23 Dec 2018 at 16:17, Patrick Valsecchi wrote:
> I did a tcpdump. My config is modified to point to a local container (www)
> in a docker compose (I'm trying to simplify my setup).
I did a tcpdump. My config is modified to point to a local container
(www) in a docker compose (I'm trying to simplify my setup). You can see
the DNS answers correctly:
16:06:00.181533 IP (tos 0x0, ttl 64, id 63816, offset 0, flags [DF],
proto UDP (17), length 68)
127.0.0.11.53 >
Hi,
Since haproxy version 1.8.14 and including the last 1.9 release, haproxy
puts all my backends in MAINT after around 31s. They first work fine,
but then they are put in MAINT.
The logs look like that:
<149>Dec 23 12:45:11 haproxy[1]: Proxy www started.
<149>Dec 23 12:45:11 haproxy[1
8 matches
Mail list logo
