mirror of
https://github.com/haproxy/haproxy.git
synced 2026-02-03 20:39:41 -05:00
870e2d3f1f
We now update the session's tracked counters with the observed glitches. In order to avoid incurring a high cost, e.g. if many small frames contain issues, we batch the updates around h2_process_demux() by directly passing the difference. Indeed, for now all functions that increment glitches are called from h2_process_demux(). If that were to change, we'd just need to keep the value of the last synced counter in the h2c struct instead of the stack. The regtest was updated to verify that the 3rd client that does not cause issue still sees the counter resulting from client 2's mistakes. The rate is also verified, considering it shouldn't fail since the period is very long (1m). |
||
|---|---|---|
| .. | ||
| ca-auth.crt | ||
| cli_src_dst.vtc | ||
| client1.pem | ||
| common.pem | ||
| dispatch.vtc | ||
| h2_glitches.vtc | ||
| http_reuse_aggressive.vtc | ||
| http_reuse_always.vtc | ||
| http_reuse_be_transparent.vtc | ||
| http_reuse_conn_hash.vtc | ||
| http_reuse_dispatch.vtc | ||
| http_reuse_never.vtc | ||
| http_reuse_safe.vtc | ||
| proxy_protocol_random_fail.vtc | ||
| proxy_protocol_send_generic.vtc | ||
| proxy_protocol_send_unique_id.vtc | ||
| proxy_protocol_send_unique_id_alpn.vtc | ||
| proxy_protocol_tlv_validation.vtc | ||
| reverse_connect_full.vtc | ||
| reverse_server.vtc | ||
| reverse_server_name.vtc | ||
| tcp_to_http_upgrade.vtc | ||