DOC: config: fix misplaced "bytes_{in,out}"

Counters are managed at the stream level and also work in TCP mode.

They were found in the Layer 7 section, moving them to the Layer 4
section instead.

This could be backported in 2.9 with fa0a304f3 ("DOC: config: add an
index of sample fetch keywords")
This commit is contained in:
Aurelien DARRAGON 2024-02-07 17:23:56 +01:00
parent 8126d3b007
commit ad8625cb64

View File

@ -21046,6 +21046,8 @@ bc_rtt(<unit>) integer
bc_rttvar(<unit>) integer
be_server_timeout integer
be_tunnel_timeout integer
bytes_in integer
bytes_out integer
cur_server_timeout integer
cur_tunnel_timeout integer
cur_client_timeout integer
@ -21344,6 +21346,12 @@ be_tunnel_timeout : integer
current backend. This timeout can be overwritten by a "set-timeout" rule. See
also the "cur_tunnel_timeout".
bytes_in : integer
This returns the number of bytes uploaded from the client to the server.
bytes_out : integer
This is the number of bytes transmitted from the server to the client.
cur_server_timeout : integer
Returns the currently applied server timeout in millisecond for the stream.
In the default case, this will be equal to be_server_timeout unless a
@ -23476,8 +23484,6 @@ base string
base32 integer
base32+src binary
baseq string
bytes_in integer
bytes_out integer
capture.req.hdr(<idx>) string
capture.req.method string
capture.req.uri string
@ -23615,12 +23621,6 @@ baseq : string
instead of "base" allows one to properly identify the target resource, for
statistics or caching use cases. See also "path", "pathq" and "base".
bytes_in : integer
This returns the number of bytes uploaded from the client to the server.
bytes_out : integer
This is the number of bytes transmitted from the server to the client.
capture.req.hdr(<idx>) : string
This extracts the content of the header captured by the "capture request
header", idx is the position of the capture keyword in the configuration.