- From: Christer Holmberg <christer.holmberg@ericsson.com>
- Date: Mon, 28 Jun 2021 12:24:35 +0000
- To: "squid3@treenet.co.nz" <squid3@treenet.co.nz>, "ietf-http-wg@w3.org" <ietf-http-wg@w3.org>
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"
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.
Regards,
Christer
Received on Monday, 28 June 2021 12:24:50 UTC