- From: Mark Nottingham <mnot@mnot.net>
- Date: Tue, 25 Feb 2020 16:05:06 +1100
- To: "Julian F. Reschke" <julian.reschke@gmx.de>
- Cc: Tommy Pauly <tpauly@apple.com>, HTTP Working Group <ietf-http-wg@w3.org>
> On 25 Feb 2020, at 11:34 am, Mark Nottingham <mnot@mnot.net> wrote: > >> >> That said, I *do* agree that the value-less variant is nice for flags; >> my question is why we ended up with special-casing this in parameters, > > The bug has the history; basically there are a number of already-defined headers that have value-less parameters that previously failed parsing as SH. *If* we want to try to back-port them in the future, accommodating that seems important. Also - experience with Cache-Status and Proxy-Status shows that it's really nice to have the value-less true. >> and also why we don't allow serialising with "true" value outside >> parameters. I'm not sure what you mean here... -- Mark Nottingham https://www.mnot.net/
Received on Tuesday, 25 February 2020 05:05:25 UTC