tree d2b649a1594edb04a38b49ee67eec3626bd97882
parent c7b4e9d499fa798a84af7e3a004c91cece062e02
author diannahu <diannahu@google.com> 1695839110 -0700
committer Copybara-Service <copybara-worker@google.com> 1695848958 -0700

Count server-sent RST_STREAM STREAM_CLOSED as suspect streams towards the HTTP/2 connection close threshold.

This CL considers scenarios in which the GFE needs to send RST_STREAM
STREAM_CLOSED as suspicious, as these scenarios imply the client is sending
HEADERS or DATA on a stream after half-closing that stream. As discussed in
cl/568690849, these scenarios can count toward the existing threshold for
connection close (used for client-sent premature RST_STREAMs) because the GFE
will not be forwarding these frames to the backend.

This CL also performs a minor fix to consider the receipt of HEADERS on a
half-closed remote stream to be suspect (via newly closing with RST_STREAM
STREAM_CLOSED) even if that HEADERS does not have the END_STREAM flag set.

Tested:
  blaze test //gfe/gfe2/http2/e2e:end_to_end_test_http2 --test_filter=*DataFrameAfterHalfClosedRemote* --runs_per_test=2000
  http://sponge2/1f334d43-ce60-4531-b7b4-aea62075e6c3

Protected by FLAGS_gfe2_reloadable_flag_http2_record_suspect_rst_stream_closed and pre-existing --gfe2_reloadable_flag_http2_send_goaway_for_premature_rst_streams.

PiperOrigin-RevId: 568909684