Upgrade: tokens

• From: Stefan Eissing <stefan.eissing@greenbytes.de>
• Date: Mon, 21 Sep 2015 14:06:22 +0200
• To: Group HTTP Working <ietf-http-wg@w3.org>
• Message-Id: <157437BA-E7E3-4617-8F40-6836628EAA61@greenbytes.de>

Implemenation raised the question if tokens in Upgrade headers are to be treated case sensitive or not (for ALPN it is clearly defined). The current status

- rfc7230 does not explicitly say so, but for other headers it does. So, one could say that Upgrade values are case-sensitive
- rfc7230 reserves tokens of flavor "HTTP*" for itself and future versions
- the ALPN value "http/1.1" is seen in the wild
- WebSocket RFC explicitly defines its token as case-insensitive

I see only interop problems should HTTP insist on case sensitive values. Does 7230 need a fix here?

Thanks, Stefan

<green/>bytes GmbH
Hafenweg 16, 48155 Münster, Germany
Phone: +49 251 2807760. Amtsgericht Münster: HRB5782

Received on Monday, 21 September 2015 12:06:47 UTC