This is useful when enabling socket-stats to know that a socket is being
waiting for some resource (RAM, global connections, etc...).
rate-limit sessions 10
server 127.0.0.1:1025
- Note : when the maximum rate is reached, the frontend's status appears as
- "FULL" in the statistics, exactly as when it is saturated.
+ Note : when the maximum rate is reached, the frontend's status is not changed
+ but its sockets appear as "WAITING" in the statistics if the
+ "socket-stats" option is enabled.
See also : the "backlog" keyword and the "fe_sess_rate" ACL criterion.
"",
U2H0(l->counters->denied_req), U2H1(l->counters->denied_resp),
U2H2(l->counters->failed_req),
- (l->nbconn < l->maxconn) ? "OPEN" : "FULL");
+ (l->nbconn < l->maxconn) ? (l->state == LI_LIMITED) ? "WAITING" : "OPEN" : "FULL");
} else {
chunk_printf(&msg,
/* pxid, name, queue cur, queue max, */