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: HRB5782Received on Monday, 21 September 2015 12:06:47 UTC
This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 17:14:46 UTC