Thank you for the fast response!
I can confirm that this patch indeed fixes the segfault.
Best,
Leo
Am Mo., 1. Apr. 2019 um 14:21 Uhr schrieb Ricardo Nabinger Sanchez
:
>
> Hi Leonhard,
>
> On Mon, 1 Apr 2019 13:14:06 +0200
> Leonhard Wimmer
> wrote:
>
> > I also m
Hi Willy, list,
I just encountered a segfault with 1.8.19 at startup and thought you
might want to check it out. I put together a small config with which I
can reproduce the crash every time:
-
global
nbthread 2
listen test
bind *:8080
mode tcp
option tcp-check
tcp-check connect
Hi,
I can confirm the issue with haproxy-1.9.4.tar.gz and Firefox 65.0 on
Linux (Ubuntu 18.10, latest Updates).
For me the files differ already at byte 5:
Correct:
1f 8b 08 00 70 e6 5a 5c 02 03 ec 5c 5b 73 e2 48 |p.Z\...\[s.H|
0010 96 ae 67 ff 0a 6d f5 43 55 75 18 6c a8 b2
Hi,
Am Do., 20. Dez. 2018 um 22:22 Uhr schrieb Vincent Bernat :
> Is it important enough for an 1.8.16? Is it important enough for
> distributors to release a fixed version? Why doesn't it affect most DNS
> implementations?
Please find attached a very short pcap with 4 packets: 2 DNS requests
n confirm that this patch indeed solves the issue in my test setup.
Best,
Leo
Am Do., 20. Dez. 2018 um 16:58 Uhr schrieb Jerome Magnin :
>
> Hi,
>
> On Thu, Dec 20, 2018 at 03:42:40PM +0100, Leonhard Wimmer wrote:
> > Hello,
> >
> > We are running HAProxy in our Do
edded DNS server.
I'm not yet sure if it is the Docker DNS server returning an invalid result
or HAProxy having a problem with the validation.
I'm happy to help with debugging. I can provide packet captures of the DNS
resolution and a sample config to reproduce the problem if you are interested.
6 matches
Mail list logo
