Handle HTTP/2 half-closed connections gracefully #775

Activity

1. lovelydinosaur commented on Aug 9, 2023

   

   lovelydinosaur

   on Aug 9, 2023

   Member

   More actions

   So the equivalent for HTTP/2 here is this...

   https://httpwg.org/specs/rfc7540.html#HttpSequence

   An HTTP response is complete after the server sends — or the client receives — a frame with the END_STREAM flag set (including any CONTINUATION frames needed to complete a header block). A server can send a complete response prior to the client sending an entire request if the response does not depend on any portion of the request that has not been sent and received. When this is true, a server MAY request that the client abort transmission of a request without error by sending a RST_STREAM with an error code of NO_ERROR after sending a complete response (i.e., a frame with the END_STREAM flag). Clients MUST NOT discard responses as a result of receiving such a RST_STREAM, though clients can always discard responses at their discretion for other reasons.

   We haven't had any users observe or request this so we don't need to treat it as high priority. Starting out with a test case for this sequence of frames would be the way to go. I'm not sure what our behaviour currently is here.
2. lovelydinosaur

   added

   http/2

   on Sep 27, 2024
3. stale commented on Apr 26, 2025

   

   stalebot

   on Apr 26, 2025 – with Stale

   More actions

   This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
4. stale

   added

   wontfixThis will not be worked onThis will not be worked on

   on Apr 26, 2025
5. stale

   closed this as completedon Jun 27, 2025