Hi Willy,
What a great new feature! Being able to limit connections/second is
something we've probably all needed for a long time. Does this system
use the failover "down" message if the client has to wait too long
before having their request served?
As I was thinking about the advantages
On Sat, Mar 07, 2009 at 07:50:26PM +0800, Jeffrey 'jf' Lim wrote:
> > Probably that the feature will be improved so that we can decide by
> > configuration what type of errors should cause the request/response
> > to be captured.
> >
>
> or where it should get logged to? it sounds like right now i
On Sat, Mar 7, 2009 at 7:32 PM, Willy Tarreau wrote:
> Hi Jeff,
>
> On Sat, Mar 07, 2009 at 07:03:15PM +0800, Jeffrey 'jf' Lim wrote:
>> Woohoo!! :) thanks, Willy, for the work. Seems like a really great
>> list of stuff there.
>>
>> Especially love the "HTTP invalid request and response captures
Hi Jeff,
On Sat, Mar 07, 2009 at 07:03:15PM +0800, Jeffrey 'jf' Lim wrote:
> Woohoo!! :) thanks, Willy, for the work. Seems like a really great
> list of stuff there.
>
> Especially love the "HTTP invalid request and response captures per
> frontend/backend" feature - I would definitely love to b
On Sat, Mar 7, 2009 at 2:38 AM, Willy Tarreau wrote:
> Hi Thomas,
>
> On Thu, Mar 05, 2009 at 08:45:20AM -0500, Allen, Thomas wrote:
>> Hi Jeff,
>>
>> The thing is that if I don't include the health check, the load balancer
>> works fine and each server receives equal distribution. I have no idea
questions that will be asked after the
> release.
>
> The current version has been running in production with tcp-splicing on a
> very big site for more than one month, and on my small site for about as
> long. I know that some of the people on the list also use it regularly.
>
6 matches
Mail list logo
