Have defined in the log format the fields:
"\"%{QS_ErrorNotes}e\" \"%{QS_IPConn}e\" \"%{QS_SrvConn}e\" \"%{QS_AllConn}e\" \"%{mod_qos_cr}e\" \"%{mod_qos_ev}e\" \"%{mod_qos_con}e\"
With http/2.0 requests, I see in the log that the fields
QS_IPConn, QS_SrvConn and QS_AllConn are always empty :
mod_http2 creates slave connections in the context of HTTP/2 request processing which are not handled by mod_qos.
I recommend to use request level control directives only when enabling HTTP/2.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Have defined in the log format the fields:
"\"%{QS_ErrorNotes}e\" \"%{QS_IPConn}e\" \"%{QS_SrvConn}e\" \"%{QS_AllConn}e\" \"%{mod_qos_cr}e\" \"%{mod_qos_ev}e\" \"%{mod_qos_con}e\"
With http/2.0 requests, I see in the log that the fields
QS_IPConn, QS_SrvConn and QS_AllConn are always empty :
"-" "-" "-" "-" "3" "-" "-"
With http/1.1 they always have value :
"-" "1" "10" "10" "3" "-" "-"
With http/2.0 is it catching nothing ?
Config:
Running Apache 2.4.53
QS_LocRequestLimitDefault 50
QS_ClientEntries 10000
QS_SrvMaxConnPerIP 25
QS_SrvMaxConnClose 50%
QS_SrvMinDataRate 150 1200
QS_SrvSampleRate 15
Cheers, Steffen
Last edit: Steffen 2022-03-21
mod_http2 creates slave connections in the context of HTTP/2 request processing which are not handled by mod_qos.
I recommend to use request level control directives only when enabling HTTP/2.