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

A suggested text about a push stream after a CANCEL_PUSH #3699

Closed
wants to merge 1 commit into from
Closed
Changes from all commits
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
7 changes: 4 additions & 3 deletions draft-ietf-quic-http.md
Expand Up @@ -1292,9 +1292,10 @@ corresponding promise to be fulfilled.
Sending CANCEL_PUSH has no direct effect on the state of existing push streams.
A server SHOULD NOT send a CANCEL_PUSH when it has already created a
corresponding push stream, and a client SHOULD NOT send a CANCEL_PUSH when it
has already received a corresponding push stream. If a push stream arrives
after a client has sent CANCEL_PUSH, this MAY be treated as a stream error of
type H3_STREAM_CREATION_ERROR.
has already received a corresponding push stream. A push stream may arrive
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
has already received a corresponding push stream. A push stream may arrive
has already received a corresponding push stream. A push stream could arrive

after a client has sent CANCEL_PUSH, because a server may have not yet processed
the CANCEL_PUSH. The client SHOULD abort reading the stream with an error code
of H3_REQUEST_CANCELLED.

A CANCEL_PUSH frame is sent on the control stream. Receiving a CANCEL_PUSH
frame on a stream other than the control stream MUST be treated as a connection
Expand Down