W3C home > Mailing lists > Public > ietf-http-wg@w3.org > April to June 2018

Re: draft-ietf-httpbis-replay-03, "5.1. The Early-Data Header Field"

From: Julian Reschke <julian.reschke@gmx.de>
Date: Tue, 15 May 2018 09:00:51 +0200
To: Mark Nottingham <mnot@mnot.net>, Kazuho Oku <kazuhooku@gmail.com>
Cc: Martin Thomson <martin.thomson@gmail.com>, Willy Tarreau <w@1wt.eu>, HTTP Working Group <ietf-http-wg@w3.org>
Message-ID: <5235afaf-34b2-4426-ac7f-0d6e91655926@gmx.de>

On 2018-05-15 07:42, Mark Nottingham wrote:
> SH doesn't allow empty header fields, FWIW.
> ...

...which makes it incompatible with the list rule in RFC 7230, no?

Received on Tuesday, 15 May 2018 07:01:49 UTC

This message: [ Message body ]
Next message: Mark Nottingham: "Re: draft-ietf-httpbis-replay-03, "5.1. The Early-Data Header Field""
Previous message: Mark Nottingham: "Re: draft-ietf-httpbis-replay-03, "5.1. The Early-Data Header Field""
In reply to: Mark Nottingham: "Re: draft-ietf-httpbis-replay-03, "5.1. The Early-Data Header Field""
Next in thread: Mark Nottingham: "Re: draft-ietf-httpbis-replay-03, "5.1. The Early-Data Header Field""
Reply: Mark Nottingham: "Re: draft-ietf-httpbis-replay-03, "5.1. The Early-Data Header Field""

Mail actions: [ respond to this message ] [ mail a new topic ]
Contemporary messages sorted: [ by date ] [ by thread ] [ by subject ] [ by author ]
Help: [ How to use the archives ] [ Search in the archives ]

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 17:15:21 UTC