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

Arrival-after-cancel is a general principle #3672

Merged
merged 1 commit into from May 19, 2020
Merged

Arrival-after-cancel is a general principle #3672

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
21 changes: 9 additions & 12 deletions draft-ietf-quic-http.md
View file
Open in desktop
Expand Up @@ -827,18 +827,13 @@ following properties:
- safe; see Section 7.2.1 of {{!SEMANTICS}}
- does not include a request body or trailer section

Clients SHOULD send a CANCEL_PUSH frame upon receipt of a PUSH_PROMISE frame
carrying a request which is not cacheable, is not known to be safe, or that
indicates the presence of a request body. If the pushed response arrives on a
push stream, this MAY be treated as a stream error of type
H3_STREAM_CREATION_ERROR.

The server MUST include a value in the ":authority" pseudo-header field for
which the server is authoritative; see {{connection-reuse}}. A client SHOULD
send a CANCEL_PUSH frame upon receipt of a PUSH_PROMISE frame carrying a request
for which it does not consider the server authoritative. If the pushed response
arrives on a push stream, this MAY be treated as a stream error of type
H3_STREAM_CREATION_ERROR.
which the server is authoritative; see {{connection-reuse}}.

Clients SHOULD send a CANCEL_PUSH frame upon receipt of a PUSH_PROMISE frame
carrying a request which is not cacheable, is not known to be safe, that
indicates the presence of a request body, or for which it does not consider the
server authoritative.

Each pushed response is associated with one or more client requests. The push
is associated with the request stream on which the PUSH_PROMISE frame was
Expand Down Expand Up @@ -1297,7 +1292,9 @@ 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.
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.

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