You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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 the server does not need to receive the remainder of the request, it MAY abort reading the request stream, send a complete response, and cleanly close the sending part of the stream. The error code H3_NO_ERROR SHOULD be used when requesting that the client stop sending on the request stream. Clients MUST NOT discard complete responses as a result of having their request terminated abruptly, though clients can always discard responses at their discretion for other reasons. If the server sends a partial or complete response but does not abort reading the request, clients SHOULD continue sending the content of the request and close the stream normally.
The text was updated successfully, but these errors were encountered:
rzikm
changed the title
[HTTP/3] correctly handle H3_NO_ERROR when sending request content
Vorrectly handle H3_NO_ERROR when sending request content
Nov 26, 2024
rzikm
changed the title
Vorrectly handle H3_NO_ERROR when sending request content
Correctly handle H3_NO_ERROR when sending request content
Nov 26, 2024
Hit in HTTP/3 stress test
According to the RFC
The text was updated successfully, but these errors were encountered: