Re: Rate Limit a URL

I am using the following configuration. But, it works like DDOS. Once it starts blocking, it blocks for ever. frontend api_gateway bind 0.0.0.0:80 mode http option forwardfor default_backend nodes # Set up stick table to track request rates #stick-table type binary len 8

Rate Limit a URL

Hi All, I want to use Haproxy to do the Rate limiting the front end URL. I tried the suggestions mentioned here. But, I see that using these, once it blocks it blocks for ever. So, this is like DDOS not the Rate limiting. My requirement is that the customer can access the URL /XYZ000/ at 1000 RP

Re: Require info on ACL for rate limiting on per URL basis.

Thanks for response and information. And I came across this link : https://www.haproxy.com/blog/introduction-to-haproxy-maps/#rate-limiting-by-url-path/ for url based rate-limit. With this exact config (copied exact config to haproxy.cfg and also created maps/rates.map file) I made one observation

H2 Protocol Errors in HTX Mode (1.9.4 & 1.9.4-dev)

Hi List, We recently started using HAProxy to act as a first point of entry for most of our traffic. We initially set it up with H2 + HTX frontend and H1.1 backend; however, this led to some strange behavior consistently reproducible on one page. Whenever we loaded this page (https://www.serm

Status Codes in H2 Mode

Hi List, Willy, After transitioning to 1.9.4, I can say things are much more stable when using h2 on the frontend. Thanks for all the bug fixes and patches since 1.9.0! I'll be upgrading to 1.9.5 when it comes out, so I'm looking forward to that. I have one question: we track error rates across

Re: error in haproxy 1.9 using txn.req:send in lua

Hi Thierry, Thank you for this detailed steps, I'll give it a try. Best regards Laurent On 21/02/2019 23:40, "Thierry Fournier" wrote: Hi, You can use something like that: --> receive request from client --> frontend a --> use-service lua.xxx -->