- From: Christer Holmberg <christer.holmberg@ericsson.com>
- Date: Mon, 28 Jun 2021 10:43:54 +0000
- To: Julian Reschke <julian.reschke@gmx.de>, "ietf-http-wg@w3.org" <ietf-http-wg@w3.org>
Hi Julian, Eventhough the generic syntax allows both tokens and quoted-strings for parameter values, I don't think it means that you by default can use both for a particular parameter. If it does, I think it should be explicitly stated. Regards, Christer -----Original Message----- From: Julian Reschke <julian.reschke@gmx.de> Sent: maanantai 28. kesäkuuta 2021 12.58 To: ietf-http-wg@w3.org Subject: Re: Editorial issues with RFC 7616 Am 28.06.2021 um 11:45 schrieb Christer Holmberg: > ... > Q3: > > Section 3.3 of RFC 7616 lists the allowed WWW-Authenticate parameters. > But, there is no syntax for them. At the end of Section 3.3 there is > text saying which parameters should be encoded as quoted-strings, and > which should not be encoded as quoted-strings. But, for the 'charset' > and 'userhash' parameters there is no text. Should they be encoded as > quoted-strings or not, or can they be both? > ... The syntax is generic, as defined in <https://protect2.fireeye.com/v1/url?k=4b20e57b-14bbdc3f-4b20a5e0-861d41abace8-a333515a382dca50&q=1&e=32427685-fb2e-4541-99c4-0473c981d15a&u=https%3A%2F%2Fgreenbytes.de%2Ftech%2Fwebdav%2Frfc7235.html%23challenge.and.response>. For the other issues I would recommend to raise errata. Best regards, Julian
Received on Monday, 28 June 2021 10:44:25 UTC