Hi Cyril,
On Tue, Jan 14, 2014 at 08:23:00AM +0100, Willy Tarreau wrote:
Hey, excellent catch! You're absolutely right. I'm totally ashamed
for not having found it while reading the code. I was searching for
a place where a wrong computation could lead to something larger
than the buffer and
OK here's a proposed fix which addresses the API issue for both
raw_sock and ssl_sock.
Steve, it would be nice if you could give it a try just to confirm
I didn't miss anything.
Thanks,
Willy
From 3e499a6da1ca070f23083c874aa48895f00d0d6f Mon Sep 17 00:00:00 2001
From: Willy Tarreau w...@1wt.eu
Just a simple though on health checks after a soft reload of HAProxy
If for example you had several backend servers one of which had crashed...
Then you make make a configuration change to HAProxy and soft reload,
for instance adding a new backend server.
All the servers are instantly
Lukasz Michalski lm@... writes:
I setup two haproxy instances - one in tcp mode for protocol detection
and the second one for routing http requests application servers.
Works like a charm on my development machine.
Thanks again!
Łukasz
Dear Lukasz,
Could you maybe post the config
Hi,
we are using HAProxy 1.5-dev21 as loadbalancer frontend and some NGINX
1.4 servers as backend. Everything is working perfect. Great piece of
software!
One question:
If some client sends a request like:
GET something.someone
This request is forwarded to the backends even if it is not a
Hi again Willy,
Le 14/01/2014 12:22, Willy Tarreau a écrit :
OK here's a proposed fix which addresses the API issue for both
raw_sock and ssl_sock.
Steve, it would be nice if you could give it a try just to confirm
I didn't miss anything.
OK, from my side, now I'm on the laptop where I can
Willy, have you validated this version in our lab as well
Baptiste
Le 14 janv. 2014 19:21, Cyril Bonté cyril.bo...@free.fr a écrit :
Hi again Willy,
Le 14/01/2014 12:22, Willy Tarreau a écrit :
OK here's a proposed fix which addresses the API issue for both
raw_sock and ssl_sock.
Steve,
Patched and confirmed in our environment that this is now working / seems
to have fixed the issue. Thanks!
Steve Ruiz
On Tue, Jan 14, 2014 at 3:22 AM, Willy Tarreau w...@1wt.eu wrote:
OK here's a proposed fix which addresses the API issue for both
raw_sock and ssl_sock.
Steve, it would be
I searched for monitor in the archives and read back about a year, and didn't
see this asked. I did see
Apologies if it's something that has already been asked and answered.
In my application it would be useful to have multiple monitors, because I'd
like to use HAProxy as a poor man's
On Tue, Jan 14, 2014 at 12:25:37PM -0800, Steve Ruiz wrote:
Patched and confirmed in our environment that this is now working / seems
to have fixed the issue. Thanks!
Great, many thanks to you both guys. We've got rid of another pretty
old bug, these are the ones that make me the happiest once
Hi!
Thanks for your reply!
We finally found out that the directive in our haproxy.conf
tcp-request inspect-delay 30s
made this error happened.
I think this because the global settings in our defualts:
timeout client 60s
---
But the tcp-request inspect-delay 30s in
Hi!
In today repository abf08d, compile error/warning occurred as below.
My OS Environment
: CentOS 6.4 x86_64
In file included from src/listener.c:18:
include/common/accept4.h:61: error: static declaration of 'accept4' follows
non-static declaration
/usr/include/sys/socket.h:222: note:
Hello,
Is it possible to forward an incoming request to the *backend *by retaining
the URL path in *http *mode?.
Using *ACLs *I was able to categorize the incoming requests to different
rulesets, but on using a specific *backend *for a certain URL parth, I
could not figure out how to send the
2014/1/15 Ge Jin altman87...@gmail.com:
Hi!
Thanks for your reply!
We finally found out that the directive in our haproxy.conf
tcp-request inspect-delay 30s
made this error happened.
I think this because the global settings in our defualts:
timeout client 60s
14 matches
Mail list logo
