Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Recommend H3_NO_ERROR for early responses #3208

Merged
merged 2 commits into from Dec 9, 2019
Merged

Recommend H3_NO_ERROR for early responses #3208

Changes from 1 commit
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
6a72f42
Recommend H3_NO_ERROR for early responses
MikeBishop Nov 8, 2019
f8efc92
Clarify what the error code is for
MikeBishop Nov 8, 2019
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
14 changes: 7 additions & 7 deletions draft-ietf-quic-http.md
View file
Open in desktop
Expand Up @@ -425,13 +425,13 @@ 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
MikeBishop marked this conversation as resolved.
Show resolved Hide resolved
complete response, and cleanly close the sending part of the stream. In this
situation, the error code H3_NO_ERROR SHOULD be used. 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, clients SHOULD continue sending the body of the request and close the
stream normally.
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, clients SHOULD continue sending
the body of the request and close the stream normally.


### Header Formatting and Compression {#header-formatting}
Expand Down