Hi,
for logging I have:
=====================================
global
log /dev/log local1
defaults
log global
option log-health-checks
option log-separate-errors
listen myname00 127.0.0.1:8090
mode http
option httplog
option dontlog-normal
=====================================
I see a lot of these:
Jan 6 09:18:47 myname haproxy[17508]: 127.0.0.1:36688
[06/Jan/2014:09:18:37.521] myname00 myname00/myname01 0/0/0/79/10175 200
7482 - - cD-- 2/2/2/2/0 0/0 "CONNECT whatever.com:443 HTTP/1.0"
The method varies between GET, POST and CONNECT, so this seems not to be
related. It is also not related to health checks.
The recurring element seems to be "cD--" which translates to
first event which caused the session to terminate
c : the client-side timeout expired while waiting for the
client to send or receive data.
Actually I do not care if some client vanished into nirvana. :-)
Is there a configuration option to not log client timeouts?
If not: is this the thing to do with a private patch?
proto_http.c / http_sess_clflog()
-err = (s->flags & (SN_ERR_MASK | SN_REDISP)) ||
+err = (s->flags & ((SN_ERR_MASK & ~SN_ERR_CLITO) | SN_REDISP)) ||
Kind regards,
Robert
