Re: rate limit by virtual host

Hi Fabien,

There are new rate liming features that have been introduced into the 1.5 dev builds. I am using them in production and it has been stable for me. I wrote a introduction to some of the features at http://blog.serverfault.com/post/1016491873/better-rate-limiting-for-all-with-haproxywhich might be helpful to you. The updated documentation of course goes into more detail.

-Kyle

On Mon, Sep 20, 2010 at 10:55 AM, Fabien Germain <fabien.germain#gmail.com>wrote:

> Hello,
>
> On Wed, Jan 27, 2010 at 10:22 AM, Fabien Germain <fabien.germain#gmail.com
> > wrote:
>
>> On Tue, Jan 26, 2010 at 1:21 PM, Willy Tarreau <w#1wt.eu> wrote:
>> [...]
>> >> * Is there a cleverer way to do it ? I mean : if I have 2000 domains
>> >> hosted on the cluster, it means 2000 ACL and 2000 backend sections :
>> >> Not really easy to maintain... Do I have a generic way to handle
>> >> domains ?
>> >
>> > Right now, there is not. However, I have started to work on a draft
>> > for generic QoS per any criterion relying on the new stickiness code.
>> > That way you could create many classes of limitations and decide whether
>> > a request is subject to that limitation. You could then have limits per
>> > backend, per frontend, per server, and per source IP, header, etc...
>> >
>> > I think I will start doing that for 1.5, as 1.4 is getting very close
>> > to a release, I don't want to break anything now.
>>
>> Great news !
>>
>
> I come back to this previous thread I opened in january, about generic QoS
> per any criterion : Do you have any idea when it will be available ? It
> would be so wonderful :-)
>
>
> Thanks for your great work, we love haproxy !
>
> Fabien
>
Received on 2010/09/20 17:00