- From: Julian Reschke <julian.reschke@gmx.de>
- Date: Tue, 12 May 2020 22:17:39 +0200
- To: Poul-Henning Kamp <phk@phk.freebsd.dk>
- Cc: Ian Clelland <iclelland@google.com>, Willy Tarreau <w@1wt.eu>, HTTP Working Group <ietf-http-wg@w3.org>
On 12.05.2020 21:34, Poul-Henning Kamp wrote: > -------- > In message <4045931b-06b3-9b76-106f-773499b8374b@gmx.de>, Julian Reschke writes: > >> Going back to the SH spec: I'm afraid that the spec *disallows* to fail >> early on garbage - is this *really* the intent? > > Ehhh... what ? > > 1.1. Intentionally Strict Processing > > This specification intentionally defines strict parsing and > serialisation behaviours using step-by-step algorithms; the only > error handling defined is to fail the operation altogether. > > Since the only failure is total failure, why or even how would you go > about postponing it ? The issue here is that combining Foo: "a and Foo: b" into Foo: "a, b" *hides* an issue, and no failure will occur. Furthermore, we not only get no failure, but the resulting string may vary depending on how the fields were combined. I get that it's unavoidable that this *can* happen, but does this mean we should *disallow* failing for that input? Best regards, Julian
Received on Tuesday, 12 May 2020 20:18:21 UTC