Not the tarpit feature, that will deny access to the content with 500 status. I don't want to kill the request, just delay it,
On Fri, Aug 5, 2016 at 8:57 PM, Dennis Jacobfeuerborn <[email protected] > wrote: > On 05.08.2016 19:11, CJ Ess wrote: > > So I know I can use Haproxy to send 429s when a given request rate is > > exceeded. > > > > I have a case where the "user" is mostly screen scrapers and click bots, > so > > if I return a 429 they'll just turn around and re-request until > successful > > - I can't expect them to voluntarily manage their request rate or do any > > sort of back-off when requests fail. So instead I want to keep the > > connections open and the requests alive, and just delay dispatching them > to > > an upstream backend. Is there anyway I can do something like this? I'm > open > > to suggestions of alternative ways to achieve the same effect. > > > > It sounds like the tarpit functionality is what you want: > https://cbonte.github.io/haproxy-dconv/1.6/configuration.html#reqtarpit > > Regards, > Dennis > > >
