From afc9b546eb303617078a4d46f207c3528f809452 Mon Sep 17 00:00:00 2001 From: Martin Thomson Date: Tue, 24 Apr 2018 23:16:19 +1000 Subject: [PATCH 1/2] Document some of the properties of Early-Data According to RFC 7231, Section 8.3.1. --- draft-ietf-httpbis-replay.md | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a/draft-ietf-httpbis-replay.md b/draft-ietf-httpbis-replay.md index a06b75f39..30e7c9bd7 100644 --- a/draft-ietf-httpbis-replay.md +++ b/draft-ietf-httpbis-replay.md @@ -269,6 +269,7 @@ the `Early-Data` header field if it might have forwarded the request prior to handshake completion (see {{be-consistent}} for details). An intermediary MUST NOT remove this header field if it is present in a request. +`Early-Data` MUST NOT appear in a `Connection` header field. The `Early-Data` header field is not intended for use by user agents (that is, the original initiator of a request). Sending a request in early data implies @@ -282,6 +283,13 @@ marked with Early-Data was sent in early data on a previous hop. Requests that contain the Early-Data field and cannot be safely processed MUST be rejected using the 425 (Too Early) status code. +The `Early-Data` header field carries a single bit of information and clients +MUST include at most one instance. However multiple instances MUST be treated +as equivalent to a single instance by a server. + +A `Early-Data` header field MUST NOT be included in responses or request +trailers. + ## The 425 (Too Early) Status Code {#status} From ce2bdcfccf484f1e8cc0ced5811f3a6b6d797740 Mon Sep 17 00:00:00 2001 From: Martin Thomson Date: Thu, 26 Apr 2018 09:17:29 +0200 Subject: [PATCH 2/2] However, --- draft-ietf-httpbis-replay.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/draft-ietf-httpbis-replay.md b/draft-ietf-httpbis-replay.md index 30e7c9bd7..6f109c07b 100644 --- a/draft-ietf-httpbis-replay.md +++ b/draft-ietf-httpbis-replay.md @@ -284,8 +284,8 @@ contain the Early-Data field and cannot be safely processed MUST be rejected using the 425 (Too Early) status code. The `Early-Data` header field carries a single bit of information and clients -MUST include at most one instance. However multiple instances MUST be treated -as equivalent to a single instance by a server. +MUST include at most one instance. Multiple instances MUST be treated as +equivalent to a single instance by a server. A `Early-Data` header field MUST NOT be included in responses or request trailers.