- From: Julian Reschke <julian.reschke@gmx.de>
- Date: Fri, 10 Aug 2018 07:09:37 +0200
- To: Amos Jeffries <squid3@treenet.co.nz>, ietf-http-wg@w3.org
On 2018-08-10 05:48, Amos Jeffries wrote: > On 10/08/18 11:25, Mike Bishop wrote: >> Ick. This looks like a 6455 erratum – the registration is “WebSocket” >> but all the (non-normative) examples are “websocket”. Case-insensitive >> matching is explicitly permitted, and RFC2616/2817 don’t clearly say >> that Upgrade tokens are or aren’t case-sensitive that I can find. (Nor >> do I see it in 7230…?) >> > > I was of the understanding that Upgrade labels are governed by the > relevant protocols equivalent of RFC 7230 section 2.6 rules. So for > example HTTP labels *are* case sensitive, but WebSockets is free to > define sensitivity for its own label. > ... Is it? What if the code that handles the Upgrade token is protocol-agnostic? The problem here is that the IANA registry is first-come-first-serve, and also doesn't have a "case-insensitive" flag. IMHO it would be better to just fix the protocol (ws over h2) - it's not even published yet after all. Best regards, Julian
Received on Friday, 10 August 2018 05:10:14 UTC