Hi Andreas,
Le 08/04/2014 12:22, Andreas Mock a écrit :
Hi all,
I'm using haproxy snapshot 20140401 at the moment.
I'm pretty sure to have a straight forward configuration:
--------------------8<----------------
(...)
Now, when the first request comes in I see in the log the
following timing values (Tq '/' Tw '/' Tc '/' Tr '/' Tt*)
which are o.k.
7/0/0/255/263
As soon as I request the second page while keep alive is still alive,
I get the following values:
2548/0/0/668/3217
So, it seems that the measures refer to the initial session startup
time. Is this true?
Not exactly, it refers to the end of the previous request.
Is this the intended behaviour?
I'm asking because documentations says "[...] Large
times here generally indicate network trouble between the client and
haproxy.[...]" which is not the case in my scenario.
Yes, this behaviour is documented somewhere else when using "option
http-server-close" or "option http-keep-alive".
http://cbonte.github.io/haproxy-dconv/configuration-1.5.html#option%20http-server-close
"(...)At the moment, logs will not indicate whether requests came from
the same session or not. The accept date reported in the logs
corresponds to the end of the previous request, and the request time
corresponds to the time spent waiting for a new request. (...)"
--
Cyril Bonté
