Hi,
This is a friendly bot that watches fixes pending for the next haproxy-stable
release! One such e-mail is sent periodically once patches are waiting in the
last maintenance branch, and an ideal release date is computed based on the
severity of these fixes and their merge date. Responses
Hi,
This is a friendly bot that watches fixes pending for the next haproxy-stable
release! One such e-mail is sent periodically once patches are waiting in the
last maintenance branch, and an ideal release date is computed based on the
severity of these fixes and their merge date. Responses
Hello,
just build 2.1.0 on OpenBSD.. while the actual processing (fe->be)
works,
I am getting quite some weird logging (in /var/log/messages) per
http-request:
Nov 30 23:01:05 tyo haproxy: vfprintf %s NULL in ">%s %2d
%02d:%02d:%02d %.*s%*s"
syslog.conf pretty straight forward:
Hi.
Looks like it works as designed because currently are used the "str*cmp"
functions for matching. Your solution with hex convert looks like how the '\0'
byte issue could be fixed.
(CCing Thierry Fournier as maintainer of the pattern matching part)
> We use HAProxy in TCP Mode for non-HTTP protocols.
>
> The request of one particular protocol looks like this:
> - length of message (binary value, 4 bytes long)
> - binary part (40-200 bytes)
> - XML part
>
> Goal: We
5 matches
Mail list logo
