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

HTTP: server may interleave DUPLICATE_PUSH frames as well #3235

Merged
merged 2 commits into from Dec 16, 2019
Merged

HTTP: server may interleave DUPLICATE_PUSH frames as well #3235

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
28a2c38
HTTP: server may interleave DUPLICATE_PUSH frames as well
Nov 15, 2019
a57490b
Update draft-ietf-quic-http.md
dtikhonov Dec 3, 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
9 changes: 5 additions & 4 deletions draft-ietf-quic-http.md
View file
Open in desktop
Expand Up @@ -379,10 +379,11 @@ An HTTP message (request or response) consists of:
3. optionally, trailing headers, if present (see {{!RFC7230}}, Section 4.1.2),
sent as a single HEADERS frame.

A server MAY send one or more PUSH_PROMISE frames (see {{frame-push-promise}})
before, after, or interleaved with the frames of a response message. These
PUSH_PROMISE frames are not part of the response; see {{server-push}} for more
details.
A server MAY send one or more PUSH_PROMISE (see {{frame-push-promise}}) or
DUPLICATE_PUSH (see {{frame-duplicate-push}}) frames before, after, or
interleaved with the frames of a response message. These PUSH_PROMISE and
DUPLICATE_PUSH frames are not part of the response; see {{server-push}} for
more details.

Frames of unknown types ({{extensions}}), including reserved frames
({{frame-reserved}}) MAY be sent on a request or push stream before, after, or
Expand Down