A couple of possible options... You could use tcp-request inspect-delay to delay the response a number of seconds (and accept it quick if legitimate traffic). You could use redirects which will have the clients do more requests (Possibly with the inspect delays).
That said, it would be useful to force a client connection closed at times, but there are ways to protect the backends and slow some clients without completely blocking them. On Wed, Nov 18, 2020 at 3:14 AM Tim Düsterhus, WoltLab GmbH < [email protected]> wrote: > Lukas, > > > The reason is that we want to avoid outright blocking with e.g. a 429 > Too Many Requests, because that could affect legitimate traffic. Forcing > the client to re-establish the connection should not be noticeable for a > properly implemented client, other than an increased latency. > > I'm aware that this will be more costly for us as well, but we have > plenty of spare capacity at the load balancers. > > >
