From 35e4f20e72b2cfcc265e3bee66e0487d713e77bb Mon Sep 17 00:00:00 2001 From: Mike Bishop Date: Tue, 28 Aug 2018 10:57:09 -0700 Subject: [PATCH] Don't discuss pushed headers as much --- draft-ietf-quic-http.md | 9 ++++----- 1 file changed, 4 insertions(+), 5 deletions(-) diff --git a/draft-ietf-quic-http.md b/draft-ietf-quic-http.md index e62d2c290f..2209c5b425 100644 --- a/draft-ietf-quic-http.md +++ b/draft-ietf-quic-http.md @@ -294,11 +294,10 @@ response may contain zero or more header blocks containing the message headers of informational (1xx) HTTP responses (see {{!RFC7230}}, Section 3.2 and {{!RFC7231}}, Section 6.2). -PUSH_PROMISE frames (see {{frame-push-promise}}) MAY be interleaved with the -frames of a response message indicating a pushed resource related to the -response. These PUSH_PROMISE frames are not part of the response, but carry the -headers of separate HTTP request messages. See {{server-push}} for more -details. +A server MAY interleave one or more PUSH_PROMISE frames (see +{{frame-push-promise}}) with the frames of a response message indicating a +pushed resource related to the response. These PUSH_PROMISE frames are not part +of the response; see {{server-push}} for more details. The "chunked" transfer encoding defined in Section 4.1 of {{!RFC7230}} MUST NOT be used.