On Sat, May 10, 2014 at 07:58:25AM +0200, Willy Tarreau wrote:
May I ask about the ETA on this?
It's too early for me to know, I need to go down deep into the ebtrees first
to
see if longest match is compatible with strings storage-wise, then I need to
study how patterns are built as
Si ce message ne s'affiche pas correctement consultez-le en ligne
SUPER PROMO
À PARTIR DE 1,99€ LA BALLE
TITLEIST PRO V1 / PRO V1X
Balles d'occasion ou balles recyclées
Pour améliorer votre Putting:
Deux allées réversibles pour varier le niveau d’entraînement (2.5cm et
We are sorry that you decided to opt-out.
We confirm that this email account haproxy@formilux.org has un-subscribed.
Hi Lukas,
On Fri, May 09, 2014 at 10:32:39PM +0200, Lukas Tribus wrote:
Since there seemed to be no objection, I'd rather remove them before
the release. Do you already have a patch ready for this or should I
get rid of them now (and update the README) ?
Agreed. I didn't prepare a patch
Hi,
On Thu, May 08, 2014 at 06:22:11PM +0200, Lukas Tribus wrote:
Hi,
Hello,
I have few backends which are routed to regarding of URL path. Also one
of servers uses NTLM.
As it was written on many places NTLM can only function with tunnel
mode enabled. I understand that, but
NTLM an server-close are mutually incompatible.
As Willy stated, best solution for you is to use http-keep-alive mode
and upgrade to haproxy 1.5.
Baptiste
On Sat, May 10, 2014 at 1:38 PM, Willy Tarreau w...@1wt.eu wrote:
Hi,
On Thu, May 08, 2014 at 06:22:11PM +0200, Lukas Tribus wrote:
Hi,
Hi Simon,
The following compilation directive should do the trick for you USE_PCRE=1.
Baptiste
On Wed, May 7, 2014 at 10:31 AM, k simon chio1...@gmail.com wrote:
Hi,Lists,
I found I can not share the same regex txt for haproxy and squid. And
I noticed that haproxy use OS libc's regex by
Hi all,
we're almost done!
Now the bind-process mess is fixed so that we now support per-listener
process binding using the process bind keyword, which ensures that
we won't need to change the config format during the stable release if
we want to slightly improve it. And that allows us to have
Since upgrading to haproxy 1.5-dev25 I am getting the following error when
trying to detect if the SPDY/3.1 protocol is being used:
error detected while parsing ACL 'npn_spdy' : unknown matching method
'spdy/3.1' when parsing ACL expression.
The config in question:
bind :443 ssl crt
On 07 мая 2014 г., at 18:24, Emeric Brun eb...@exceliance.fr wrote:
Hi All,
I suspect FreeBSD to not support process shared mutex (supported in both
linux and solaris).
I've just made a patch to add errors check on mutex init, and to fallback on
SSL private session cache in error
On Sun, May 11, 2014 at 12:19:45AM +0400, Dmitry Sivachenko wrote:
On 07 ?? 2014 ??., at 18:24, Emeric Brun eb...@exceliance.fr wrote:
Hi All,
I suspect FreeBSD to not support process shared mutex (supported in both
linux and solaris).
I've just made a patch to add errors
Hi Willy,
I wonder if I found a bug or if HAProxy's behavior has changed in a
recent release.
I'm using:
# /opt/haproxy/sbin/haproxy -vv
HA-Proxy version 1.5-dev25 2014/05/10
Copyright 2000-2014 Willy Tarreau w...@1wt.eu
Build options :
TARGET = linux2628
CPU = generic
CC = gcc
Hi Baptiste,
Le 10/05/2014 23:20, Baptiste a écrit :
(...)
In my configuration, I have the following log-format directive:
log-format %ci:%cp\ [%t]\ %ft\ %b/%s\ %Tq/%Tw/%Tc/%Tr/%Tt\ %ST\ %B\
%CC\ %CS\ %tsc\ %ac/%fc/%bc/%sc/%rc\ %sq/%bq\ %hr\ %hs\
On Sat, May 10, 2014 at 11:37 PM, Cyril Bonté cyril.bo...@free.fr wrote:
I think the behaviour has changed since dev23. I've not tested to verify it
but it may be related to the 2 commits :
http://haproxy.1wt.eu/git?p=haproxy.git;a=commit;h=e87cac16cc082fa43d5f65dd68e1244add7871c6
14 matches
Mail list logo
