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

Push stream data and PUSH_PROMISE reordering clarification #2527

Merged
merged 3 commits into from Apr 16, 2019
Merged

Push stream data and PUSH_PROMISE reordering clarification #2527

Changes from 1 commit
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
84b4cc4
Push stream data and PUSH_PROMISE reordering clarification
rmarx Mar 18, 2019
dbba914
CMOS change for consistency
rmarx Mar 19, 2019
32327c1
Update draft-ietf-quic-http.md
martinthomson Mar 24, 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
2 changes: 1 addition & 1 deletion draft-ietf-quic-http.md
View file
Open in desktop
Expand Up @@ -1210,7 +1210,7 @@ the promise that it fulfills, then contains a response to the promised request
using the same format described for responses in {{request-response}}. Due to
reordering, data on a push stream can arrive before the corresponding
PUSH_PROMISE, in which case both the associated client request and the pushed
request headers are unknown. Clients which receive a new push stream with an
request headers are unknown. Clients that receive a new push stream with an
as-yet-unknown Push ID can buffer the stream data in expectation of the matching
PUSH_PROMISE. A client can use stream flow control (see section 4.1 of
{{QUIC-TRANSPORT}}) to limit the amount of data a server may commit to the
Expand Down