Re: resolvers hold valid clarification

with servers in this state for a long time. Can anyone confirm my understating of this setting ? śr., 22 wrz 2021 o 19:52 Michał Pasierb napisał(a): > I would like to clarify how *hold valid* is used by resolvers. I have > this configuration: > > resolvers mydns >

resolvers hold valid clarification

I would like to clarify how *hold valid* is used by resolvers. I have this configuration: resolvers mydns nameserver dns1 192.168.122.202:53 accepted_payload_size 8192 timeout resolve 5s timeout retry 2s resolve_retries 3 hold other 30s hold refused120s hold nx

no log on http-keep-alive race

Hello, I have situation where HAProxy receives a request but doesn't log it. I would like to know if this is desired behaviour or this is an actual bug. To replicate this issue: 1) create HAProxy config which doesn't disable http-keep-alive 2) on backend server set http-keep-alive timeout to a

Re: confused by HAProxy log line

Aleksandar Lazic wrote: > Am 11.10.2018 um 10:33 schrieb Michał Pasierb: > > Hello, > > > > I have a problem understanding a particular log line from HAProxy 1.7.11 > in > > production system. My clients report problems from time to time. They > make

confused by HAProxy log line

Hello, I have a problem understanding a particular log line from HAProxy 1.7.11 in production system. My clients report problems from time to time. They make another request and all is OK. This is the log format used: log-format %tr\ %ci:%cp\ %ft\ %b/%s\ %TR/%Tw/%Tc/%Tr/%Ta\ %ST\ %B\ %CC\ %CS\

gzip compression and logging response size

Hi, I would like to log size of response before and after compression. Is it possible ? I see this question was asked before at http://thread.gmane.org/gmane.comp.web.haproxy/10008 without any resolution. Regards, Michal

regression in 1.6.13 - wrong http status in logs and stats

Hi, I would like to report a regression in HAProxy 1.6.13 after upgrading from 1.6.9 in production :( Reproduce with config: --- global log 127.0.0.1 local0 log 127.0.0.1 local1 notice maxconn 4096 chroot /usr/share/haproxy uid 99 gid 99 daemon defaults log global mode

HTTP keep-alive reuse count & max-age

Hi, Is it possible to influence how HAProxy handles HTTP keep-alives to backend servers ? I want it to close TCP connection after x many HTTP requests. Also a max-age time for single TCP connection cloud be useful. These features are available in F5 LTM OneConnect (

cookie prefix & option httpclose

Hi, I have a question about cookie prefix mode. I use configuration like this: backend b1 balance roundrobin cookie JSESSIONID prefix server s1 192.168.122.1:8080 cookie c1 Now the docs https://cbonte.github.io/haproxy-dconv/configuration-1.6.html#4-cookie for prefix say: Since all