Is there an ETA for this fix making its way to a 1.4 release? Also, is it known
what version introduced undesirable behavior with ruby clients? 1.4.9 to 1.4.18
is a fairly loose bound...
Thanks,
Bryan
-Original Message-
From: Willy Tarreau [mailto:w...@1wt.eu]
Sent: Saturday, December
Hi Bryan,
On Wed, Jan 04, 2012 at 05:23:06PM +, Cassidy, Bryan wrote:
Is there an ETA for this fix making its way to a 1.4 release? Also, is it
known what version introduced undesirable behavior with ruby clients? 1.4.9
to 1.4.18 is a fairly loose bound...
It was introduced with patch
Hi Tim,
On Tue, Dec 13, 2011 at 06:01:49PM -0500, Timothy Garnett wrote:
Hi Willy,
Thanks very much for your response. It looks like it does have something
to do with TCP_NODELAY.
Setting option http-server-close had no effect on this problem. However,
if I set option http-no-delay in
Hi Willy,
Thanks very much for your response. It looks like it does have something
to do with TCP_NODELAY.
Setting option http-server-close had no effect on this problem. However,
if I set option http-no-delay in haproxy then the problem goes away. It
also goes away if I patch Ruby's
Hi Tim,
On Mon, Dec 12, 2011 at 02:33:53PM -0500, Timothy Garnett wrote:
Hi all,
We've been using Haproxy for a couple of years now to load balance our
external traffic and our internal backend services. We recently upgraded
from version 1.4.8 to 1.4.18 and we noticed some connection
5 matches
Mail list logo
