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

Server push tidy up #1503

Merged
merged 5 commits into from Jun 29, 2018
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
6 changes: 3 additions & 3 deletions draft-ietf-quic-http.md
Expand Up @@ -527,7 +527,7 @@ but uses different mechanisms.

The PUSH_PROMISE frame ({{frame-push-promise}}) is sent on the client-initiated
bidirectional stream that carried the request that generated the push. This
allows the server push to be associated with a request. Ordering of a
allows the server push to be associated with a request. Ordering of a
PUSH_PROMISE in relation to certain parts of the response is important (see
Section 8.2.1 of {{!RFC7540}}).

Expand All @@ -546,8 +546,8 @@ exchange are carried by a PUSH_PROMISE frame (see {{frame-push-promise}})
on the request stream which generated the push. Promised requests MUST
conform to the requirements in Section 8.2 of {{!RFC7540}}.

Only servers can push; if a server receives a client-initiated push stream, this
MUST be treated as a stream error of type HTTP_WRONG_STREAM_DIRECTION.
Only servers can push; if a server receives a client-initiated push stream,
this MUST be treated as a stream error of type HTTP_WRONG_STREAM_DIRECTION.

~~~~~~~~~~ drawing
0 1 2 3
Expand Down