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

Re: Editorial issues with RFC 7616

From: Julian Reschke <julian.reschke@gmx.de>
Date: Mon, 28 Jun 2021 20:14:37 +0200
To: ietf-http-wg@w3.org
Message-ID: <37e43d9f-24d5-0b31-a7c9-a037ace4ff1a@gmx.de>
Am 28.06.2021 um 14:24 schrieb Christer Holmberg:
> Hi,
>>> 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.
>> That is exactly what it means. Either token or quoted-string can be used for any parameter value. Except parameters which are defined as needing a specific form.
> Ok, I found the following text in RFC 7231:
>     "A parameter value that matches the token production can be
>     transmitted either as a token or within a quoted-string.  The quoted
>     and unquoted values are equivalent."


> In addition, it seems like for HTTP quoted-string values are not case-sensitive, as the following examples are all equivalent:
>       text/html;charset=utf-8
>       text/html;charset=UTF-8
>       Text/HTML;Charset="utf-8"
>       text/html; charset="utf-8"

That's because it's the charset parameter. Don't generalize from that

> SIP also uses the header fields, and in SIP quoted-strings are by default *case-sensitive*, so e.g., "utf-8" and "UTF-8" would not be equivalent. But, I guess that is for SIP to sort out, if needed.

It's specific to the definition of the charset parameter in HTTP's
Content-Type field.

Best regards, Julian
Received on Monday, 28 June 2021 18:14:53 UTC

This archive was generated by hypermail 2.4.0 : Monday, 28 June 2021 18:14:54 UTC