From 63c092af9e451d864c24ca1ecd592cafc3b67e5f Mon Sep 17 00:00:00 2001 From: Lucas Pardue Date: Wed, 8 May 2019 15:48:43 +0100 Subject: [PATCH 1/2] Trigger unhappy IMO the trigger is the peer's behaviour, and the reaction by the recipient is to send a STOP_SENDING in response. I.e. we don't state the reaction is to force the remote peer to send a STOP_SENDING --- draft-ietf-quic-http.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/draft-ietf-quic-http.md b/draft-ietf-quic-http.md index a231fd4ff4..28212113c0 100644 --- a/draft-ietf-quic-http.md +++ b/draft-ietf-quic-http.md @@ -449,7 +449,7 @@ HTTP_INCOMPLETE_REQUEST. A server can send a complete response prior to the client sending an entire request if the response does not depend on any portion of the request that has not been sent and received. When this is true, a server MAY request that the -client abort transmission of a request without error by triggering a QUIC +client abort transmission of a request without error by send a QUIC STOP_SENDING frame with error code HTTP_EARLY_RESPONSE, sending a complete response, and cleanly closing its stream. Clients MUST NOT discard complete responses as a result of having their request terminated abruptly, though @@ -908,7 +908,7 @@ transport parameter `initial_max_stream_data_uni`. If the stream header indicates a stream type which is not supported by the recipient, the remainder of the stream cannot be consumed as the semantics are -unknown. Recipients of unknown stream types MAY trigger a QUIC STOP_SENDING +unknown. Recipients of unknown stream types MAY send a QUIC STOP_SENDING frame with an error code of HTTP_UNKNOWN_STREAM_TYPE, but MUST NOT consider such streams to be a connection error of any kind. From 0a67d822fbce9acf20819b4a499970ecd84bd3ba Mon Sep 17 00:00:00 2001 From: Lucas Pardue Date: Wed, 8 May 2019 15:50:45 +0100 Subject: [PATCH 2/2] ing --- draft-ietf-quic-http.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/draft-ietf-quic-http.md b/draft-ietf-quic-http.md index 28212113c0..a96e641eed 100644 --- a/draft-ietf-quic-http.md +++ b/draft-ietf-quic-http.md @@ -449,7 +449,7 @@ HTTP_INCOMPLETE_REQUEST. A server can send a complete response prior to the client sending an entire request if the response does not depend on any portion of the request that has not been sent and received. When this is true, a server MAY request that the -client abort transmission of a request without error by send a QUIC +client abort transmission of a request without error by sending a QUIC STOP_SENDING frame with error code HTTP_EARLY_RESPONSE, sending a complete response, and cleanly closing its stream. Clients MUST NOT discard complete responses as a result of having their request terminated abruptly, though