Greetings,
On 08/30/2016 05:12 PM, Chad Lavoie wrote:
Greetings,
On 08/30/2016 12:30 PM, Sam kumar wrote:
Hello Sir,
I am trying to implement rate limiting using HA proxy for my HTTP
restful services.
My requirement is to go implement below two scenario
1.URL based : Every API urls
Subject: [ANNOUNCE] haproxy-1.6.9
To: haproxy@formilux.org
Hi,
HAProxy 1.6.9 was released on 2016/08/30. It added 4 new commits after
version 1.6.8. The main fix is for a regression introduced in 1.6.8
while fixing the dead connections. Special thanks to Bartosz Koninski
for reporting it early
Greetings,
On 08/30/2016 12:30 PM, Sam kumar wrote:
Hello Sir,
I am trying to implement rate limiting using HA proxy for my HTTP
restful services.
My requirement is to go implement below two scenario
1.URL based : Every API urls will have different throttle limit
To have limits that
> What would happen if I'd configure X = 2 and the following happens:
>
> 1. Initially only 127.0.0.1 is returned.
>
1 UP server available in the backend
> 2. 127.0.0.2 is added and healthy.
>
2 servers UP available in the backend
> 3. 127.0.0.1 is removed from DNS and thus marked DOWN.
>
Greetings,
On 08/30/2016 01:10 PM, Samrat Roy wrote:
Thank you sir for your quick reply.
I am now able to give custom error code for my HAproxy configuration.
However I am facing one more issue .
With the above approach HAproxy is rejecting each and every calls once
the limit has crossed.
Hi
On 30.08.2016 01:49, Maciej Katafiasz wrote:
Right, I missed the "independent healthchecks" in the original
description, in which case it'd work well enough (albeit a low enough
TTL value is still a concern).
Thanks for the heads up. In my case this is not a concern: The DNS
server is
Hi
On 30.08.2016 09:11, Baptiste wrote:
The way we designed the feature is more like a "server template" line which
may be used to pre-configure in memory X servers sharing the same DNS
resolution.
In your case X=2. If you intend to have up to 10 servers for this service,
simply set X to 10.
Thank you sir for your quick reply.
I am now able to give custom error code for my HAproxy configuration.
However I am facing one more issue .
With the above approach HAproxy is rejecting each and every calls once the
limit has crossed. It is behaving as a circuit breaker . But my requirement
is
Hello Sir,
I am trying to implement rate limiting using HA proxy for my HTTP
restful services.
My requirement is to go implement below two scenario
1.URL based : Every API urls will have different throttle limit
2. Authorization header : Every client has unique authorization token so
using this
This config appears to be a decent start. and looks to meet your
requirements for http.
Now you just need another frontend configured for 443, it would match
the :80 frontend, aside from port, using SSL, and a path to the
certificates.
On Tue, Aug 30, 2016 at 8:47 AM, Harish Chander
If you believe this has been sent to you in error, please safely unsubscribe.
On Tue, Aug 30, 2016 at 1:49 AM, Maciej Katafiasz <
mkatafi...@purestorage.com> wrote:
> On 29 August 2016 at 16:39, Igor Cicimov
> wrote:
> > On Tue, Aug 30, 2016 at 6:18 AM, Maciej Katafiasz
> > wrote:
> >> Be aware though that DNS
13 matches
Mail list logo