Dear Sirs/Madam: We hereby sincerely invite you and your company representatives to visit our booth at The Exhibition Centre Frankfurt from Jan 9th to 12th 2018 for textile.We provide throw blanket,cushion,baby products and knit toys.We are factory and we have an advantage in price.We through the
Hi Angelo,
On Thu, Jan 4, 2018 at 11:11 PM, Angelo Hongens wrote:
> On 03-01-2018 17:39, Lukas Tribus wrote:
>>
>> To compile Haproxy 1.8 with threads, at least GCC 4.7 is needed.
>> CentOs 6 only ships GCC 4.4.7, therefor compilation fails.
>> You can disable thread support,
On 03-01-2018 17:39, Lukas Tribus wrote:
To compile Haproxy 1.8 with threads, at least GCC 4.7 is needed.
CentOs 6 only ships GCC 4.4.7, therefor compilation fails.
You can disable thread support, by adding USE_THREAD= to the make
command (nothing comes after the equal sign):
I'm no packaging
Hi William,
Verified.
Thanks for the quick fix,
Jeffrey J. Persch
On Wed, Jan 3, 2018 at 2:02 PM, Jeffrey J. Persch
wrote:
> Hi William,
>
> The test case now works. I will do load testing with the patch today.
>
> Thanks,
> Jeffrey J. Persch
>
> On Wed, Jan 3, 2018 at
Hi Devendra,
Here's a patch that I tested a little bit and apparently work for me.
Fell free to test it as well on your machine and to report here. It
fixes the build issue and allows you to run with threads.
Cheers,
Willy
>From c27bba26e5bcd772aa8b1c9a1319a2919df13f34 Mon Sep 17 00:00:00 2001
The default value of the pattern in `Socket.receive` is `*l` according
to the documentation and in the `socket.tcp.receive` method of Lua.
The default value of `wanted` in `int hlua_socket_receive(struct lua_State *)`
reflects this requirement, but the function fails to ensure this
nonetheless:
---
src/hlua.c | 14 +++---
1 file changed, 7 insertions(+), 7 deletions(-)
diff --git a/src/hlua.c b/src/hlua.c
index 285d25589..3b4fc3b54 100644
--- a/src/hlua.c
+++ b/src/hlua.c
@@ -1810,19 +1810,19 @@ connection_empty:
return 0;
}
-/* This Lus function gets two parameters.
Hi guys,
The rbtree implementation as found in haproxy, is currently unused, and has
been for quite some time.
I don't think we will need it again, so the attached patch just removes it.
Regards,
Olivier
>From 4ce3bce732fd816a835e4896646f260f0b7e6e7c Mon Sep 17 00:00:00 2001
From: Olivier
On Thu, Jan 04, 2018 at 04:03:29PM +0100, Peter Lindegaard Hansen wrote:
> Hi Willy & Lukas,
>
> I did on a test VM using the latest git version
> # haproxy -v
> HA-Proxy version 1.8.3-646d23-1 2018/01/04
> Copyright 2000-2017 Willy Tarreau
>
> And can confirm that the issues
> On 4 Jan 2018, at 15:16, Kirill A. Korinsky wrote:
>
> Honestly, I didn't.
>
> If I right understand how export-dynamic works and how haproxy use integrated
> LUA, it shouldn't have any impact.
>
> Honestly I see only one case when export-dynamic requests: when some
>
Hi Willy & Lukas,
I did on a test VM using the latest git version
# haproxy -v
HA-Proxy version 1.8.3-646d23-1 2018/01/04
Copyright 2000-2017 Willy Tarreau
And can confirm that the issues related to post+redirects are fixed for us.
And the other issue that we found seems to
Honestly, I didn't.
If I right understand how export-dynamic works and how haproxy use integrated
LUA, it shouldn't have any impact.
Honestly I see only one case when export-dynamic requests: when some
application load haproxy over dlopen, and use some function from haproxy binary
object.
I
Hi Peter,
On Wed, Jan 03, 2018 at 11:04:03PM +0100, Peter Lindegaard Hansen wrote:
> I will try to apply the patch (i am no expert at this) and see the results.
Well, don't waste your time trying to figure stuff you're not comfortable
with. I've just committed the fix and backported it. If
so it appears that OR is implicit and foo was matched as 3 acl :-)
Thank's meineerde for the help
Le 04/01/2018 à 11:45, Arnaud B. a écrit :
> Hi there,
>
> Recently, a misrouting has been found on our haproxy config. We had two
> ACL mismatching :
>
> acl foo path_reg -i
>
Hi there,
Recently, a misrouting has been found on our haproxy config. We had two
ACL mismatching :
acl foo path_reg -i
^/(w|a|i)\/([0-9]+\.){0,3}([0-9]+)?\/(ats|atc)\/.*$ OR path_reg -i
^//(w|a|i)\/([0-9]+\.){0,3}([0-9]+)?\/(ats|atc)\/.*$
and
acl bar
We use ansible without any GUI.
On the managed nodes just ssh access is needed, no agent.
This let us manage 16 haproxy 2-node-clusters (32 nodes in total)
running on two diferent linux flavors; some of the clusters have a
similar configuration, some others are completely different.
In our
Am 03.01.2018 um 23:39 schrieb Muthukumar Srinivasan - Consultant:
> Dear Sir
>
> I am looking for HA Proxy cluster management open source. we have over 100
> HA Proxy instances used for Load balancing, SSL termination etc. we need to
> manage all of them in one unified place.
>
>
> let me know if
Hi,
If the connection is redispatched, does it go to queue and wait to be served,
or is it prioritized and connected to first free slot?
Best regards,
Jakub Walecki
18 matches
Mail list logo