tree 21a31008fb5dd10c37615307555063836351369a
parent f059a0f63aaa1449cc15887a0746170a236bb283
author Willy Tarreau <w@1wt.eu> 1280856872 +0200
committer Willy Tarreau <w@1wt.eu> 1281456255 +0200

[MEDIUM] tcp: accept the "track-counters" in "tcp-request content" rules

Doing so allows us to track counters from backends or depending on contents.
For instance, it now becomes possible to decide to track a connection based
on a Host header if enough time is granted to parse the HTTP request. It is
also possible to just track frontend counters in the frontend and unconditionally
track backend counters in the backend without having to write complex rules.

The first track-fe-counters rule executed is used to track counters for
the frontend, and the first track-be-counters rule executed is used to track
counters for the backend. Nothing prevents a frontend from setting a track-be
rule nor a backend from setting a track-fe rule. In fact these rules are
arbitrarily split between FE and BE with no dependencies.