On Sun, Oct 29, 2017 at 10:17 AM, Patrick McManus <pmcmanus@mozilla.com> wrote: > +Alexey > > That interpretation doesn't seem consistent with RFC-6455, section 4.1 >> regarding absolute form (copied below). >> >> *The "Request-URI" part of the request MUST match the /resource* >> * name/ defined in Section 3 (a relative URI) or be an absolute* >> * http/https URI that, when parsed, has a /resource name/, /host/,* >> * and /port/ that match the corresponding ws/wss URI.* >> > > That's really interesting and is the only argument I find at all > compelling.Thanks. Basically its saying that the URI of the GET is not the > websockets URI used in other places such as the cache and the pac. Which is > totally insane imo. > This change happened on draft-ietf-hybi-thewebsocketprotocol-11. I see some arguments saying that it's HTTP/HTTPS until it's upgraded, in some discussion about DNS SRV and cookie handling, which happened before publication of -11. But not sure which of them is really the motivation of the change.
Received on Friday, 10 November 2017 17:28:52 UTC