On Fri, Nov 23, 2012 at 11:37:48AM +0400, Dmitry Sivachenko wrote:
On 23.11.2012 11:18, Willy Tarreau wrote:
I'd be interested in knowing if your config enables compression, because
that's an area where we very recently introduced new pools, so there could
be a relation.
It does,
On 22 November 2012 22:14, Owen Marinas omari...@woozworld.com wrote:
option httpchk POST /db/data/ext/feed/graphdb/userFeed
HTTP/1.1\r\nContent-Type: application/json\r\nContent-Length:
35\r\n{userId:8, offset:0, limit:1}\r\n
It might not be related to your original question, but I think
Hi,
I certainly missed something, but... On http://demo.1wt.eu/, you have a
split on ipv4/ipv6/local on the frontend.
This is nice to gather some traffic stats instead of parsing traffic
logs. But I cannot get the same thing in my configuration. I though
there was a line per bind, but even if
Le vendredi 23 novembre 2012 14:13:40 Baptiste a écrit :
Hi Guillaume,
In your ft configuration, just add the directive option
socket-stats.
Great, this is the option I missed, thanks !
--
Guillaume Castagnino
ca...@xwing.info / guilla...@castagnino.org
Hi,
I have one more friday's dumb question :)
Is there a way (other than sysctl -w net.ipv6.bindv6only=1) to make
the :: bind only ipv6 and not map ipv4 adresses ?
Something like the ipv6only=on from nginx ?
The goal would be to have separate sockets for '*' (v4) and '::' (v6),
keeping the
Thx for the advice Jonathan
Willy's advice from an old post was to make it work with printf+nc in
bash first. So I did.
the issue is after I added the lines to the backend(below), the server
still resported UP eben if the expected string is not there.
regards
Owen
---
On 23 November 2012 17:10, Owen Marinas omari...@woozworld.com wrote:
Thx for the advice Jonathan
Willy's advice from an old post was to make it work with printf+nc in bash
first. So I did.
I think your back-end may be being lenient, then :-)
the issue is after I added the lines to the
I hate myself for this
my production LB is running haproxy-1.4.15-1 but the Staging haproxy-1.4.8-1
after upgrade its all working now, the POST, and http-check expect
works fine.
thx all
Owen
On 12-11-23 12:50 PM, Jonathan Matthews wrote:
On 23 November 2012 17:10, Owen Marinas
On Fri, Nov 23, 2012 at 01:28:38PM -0500, Owen Marinas wrote:
I hate myself for this
my production LB is running haproxy-1.4.15-1 but the Staging haproxy-1.4.8-1
after upgrade its all working now, the POST, and http-check expect
works fine.
Good reason indeed. BTW, keep in mind that even
9 matches
Mail list logo