From a67f74d5121f01445b2de13761462cc3a4f45bf3 Mon Sep 17 00:00:00 2001 From: Mike Bishop Date: Wed, 28 Nov 2018 10:27:36 -0800 Subject: [PATCH] Which unless? --- draft-ietf-quic-http.md | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/draft-ietf-quic-http.md b/draft-ietf-quic-http.md index 055de105cf..2b95a0e507 100644 --- a/draft-ietf-quic-http.md +++ b/draft-ietf-quic-http.md @@ -870,11 +870,11 @@ response to the same request. Non-final responses do not contain a payload body or trailers. An HTTP request/response exchange fully consumes a bidirectional QUIC stream. -After sending a request, a client MUST close the stream for sending; clients -MUST NOT make stream closure dependent on receiving a response to their request, -unless using the CONNECT method (see {{the-connect-method}}). After sending a -final response, the server MUST close the stream for sending. At this point, the -QUIC stream is fully closed. +After sending a request, a client MUST close the stream for sending. Unless +using the CONNECT method (see {{the-connect-method}}), clients MUST NOT make +stream closure dependent on receiving a response to their request. After sending +a final response, the server MUST close the stream for sending. At this point, +the QUIC stream is fully closed. When a stream is closed, this indicates the end of an HTTP message. Because some messages are large or unbounded, endpoints SHOULD begin processing partial HTTP