- From: Martin Thomson <martin.thomson@gmail.com>
- Date: Sat, 12 May 2018 10:44:08 +1000
- To: Julian Reschke <julian.reschke@gmx.de>
- Cc: Kazuho Oku <kazuhooku@gmail.com>, HTTP Working Group <ietf-http-wg@w3.org>
We're already saying this about invalid constructions: The Early-Data header field carries a single bit of information and clients MUST include at most one instance. Multiple instances MUST be treated as equivalent to a single instance by a server. Why not go all out? Multiple or invalid instances of the header field MUST be treated as equivalent to a single instance with a value of 1 by a server. On Fri, May 11, 2018 at 10:42 PM Julian Reschke <julian.reschke@gmx.de> wrote: > On 2018-05-11 14:17, Kazuho Oku wrote: > > 2018-05-11 20:53 GMT+09:00 Julian Reschke <julian.reschke@gmx.de>: > >> "The Early-Data header field carries a single bit of information and clients > >> MUST include at most one instance. Multiple instances MUST be treated as > >> equivalent to a single instance by a server." > >> > >> What would that mean if what's sent is: > >> > >> Early-Data: 1 > >> Early-Data: 0 > >> > >> ? > >> > >> Or > >> > >> Early-Data: 1 > >> Early-Data: 0 > >> > >> ? > > > > Early-Data header field only takes one value: "1". Therefore, having > > multiple instances can be equal to having just one. > > ... > Understood. I'm just worried about error handling being unspecified in > cases like the above. > Best regards, Julian
Received on Saturday, 12 May 2018 00:44:45 UTC