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.

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

Rearrange discussion of cancellation and rejection #3926

Merged
merged 4 commits into from Aug 11, 2020
Merged
Changes from 1 commit
Commits
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
10 changes: 6 additions & 4 deletions draft-ietf-quic-http.md
Expand Up @@ -685,10 +685,12 @@ stream with the error code H3_REQUEST_REJECTED. In this context, "processed"
means that some data from the stream was passed to some higher layer of software
that might have taken some action as a result. The client can treat requests
rejected by the server as though they had never been sent at all, thereby
allowing them to be retried later. Servers MUST NOT use the H3_REQUEST_REJECTED
error code for requests which were partially or fully processed. When a server
abandons a response after partial processing, it SHOULD abort its response
stream with the error code H3_REQUEST_CANCELLED.
allowing them to be retried later.

Servers MUST NOT use the H3_REQUEST_REJECTED error code for requests which were
partially or fully processed. When a server abandons a response after partial
processing, it SHOULD abort its response stream with the error code
H3_REQUEST_CANCELLED.

Client SHOULD use the error code H3_REQUEST_CANCELLED to cancel requests. Upon
receipt of this error code, a server MAY abruptly terminate the response using
Expand Down