Re: Rate limiting w/o 429s

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 wrote: > On 05.08.2016 19:11, CJ Ess wrote: > > So I know I can use Haproxy to send 429s

Re: Inform backend about https for http2 connections

On 6 Aug 2016 1:31 am, "Matthias Fechner" wrote: > > Dear all, > > > I use haproxy in tcp mode to have http2 working. > Now I have the problem that the backend has to know if the connection > was encrypted or not (some websites using this information to add the > schema to css

Re: Rate limiting w/o 429s

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

Re: Rate limiting w/o 429s

Am Freitag, 5. August 2016 schrieb CJ Ess : > 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

Rate limiting w/o 429s

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

Inform backend about https for http2 connections

Dear all, I use haproxy in tcp mode to have http2 working. Now I have the problem that the backend has to know if the connection was encrypted or not (some websites using this information to add the schema to css and javascript URIs). Normally I think a reqadd X-Forwarded-Proto:\ https should

[PATCH] DOC: minor typo fixes to improve HTML parsing by haproxy-dconv

This must be backported to 1.6 and 1.5 --- doc/configuration.txt | 43 +++ 1 files changed, 23 insertions(+), 20 deletions(-) diff --git a/doc/configuration.txt b/doc/configuration.txt index fc98e5c..27e9887 100644 --- a/doc/configuration.txt +++

video

Dear: We are a Chinese company! our company needs to make a video ,the requirement is: Time Duration: 25min * 20 Episodes (500min in total) No. of Episodes: 20 Episodes Format: Full HD – High Def Video Aspect Ratio: 16:9 Widescreen If you are interested in it,contact us! Looking

Re: SEGFAULT with HAProxy 1.6.5 and server-state-file

On Fri, Aug 05, 2016 at 12:22:28PM +0200, Olivier Doucet wrote: > Hi Willy, > > 2016-08-04 18:03 GMT+02:00 Willy Tarreau : > > > Olivier, please use 1.6.7, there was a bug in the dump in 1.6.5 causing > > some incorrect data to be dumped sometimes (don't remember exactly what), > >

Re: SEGFAULT with HAProxy 1.6.5 and server-state-file

Hi Willy, 2016-08-04 18:03 GMT+02:00 Willy Tarreau : > Olivier, please use 1.6.7, there was a bug in the dump in 1.6.5 causing > some incorrect data to be dumped sometimes (don't remember exactly what), > but while I doubt it is related, at least it can needlessly complicate > your

option forwardfor except can be set only once

Hello, I just saw that 'except' can be set only once with "option forwardfor", even if config does not warn in case it is defined multiple times : listen test:80 mode http option forwardfor except 10.0.0.1 header X-IP bind *:81 server test 127.0.0.1:8080 => works listen test:80