42636 2010-07-20 06:36:21 -0700 WebSocket() constructor should throw SYNTAX_ERR if URL has zero or one slash after 'ws:' or 'wss:' 2016-05-19 02:36:22 -0700 1 1 1 Unclassified WebKit New Bugs 528+ (Nightly build) All All VERIFIED INVALID P2 Normal --- 0 zcorpan webkit-unassigned ap bfulgham joenotcharles ukai oldest_to_newest 253689 0 zcorpan 2010-07-20 06:36:21 -0700 WebKit implies the slashes if they're missing in WebSocket URLs. new WebSocket('ws:example.org/'); new WebSocket('ws:/example.org/'); Apparently no slashes means no authority (user/pass+host+port), which doesn't make sense for websocket, and websocket requires an absolute URL. So I think the above cases should throw SYNTAX_ERR. Also see https://bugzilla.mozilla.org/show_bug.cgi?id=580234 253786 1 ap 2010-07-20 10:10:44 -0700 Mozilla folks seem to disagree that this is a bug, and I think they are right. 315518 2 ap 2010-11-30 21:41:03 -0800 http://www.w3.org/Bugs/Public/show_bug.cgi?id=10213 1194621 3 bfulgham 2016-05-18 21:26:46 -0700 Since Mozilla and Alexey think current behavior is correct, closing this. 1194708 4 zcorpan 2016-05-19 02:35:02 -0700 https://www.w3.org/Bugs/Public/show_bug.cgi?id=17772#c5 e.g. for ws:example.org/ (no base url) https://url.spec.whatwg.org/#scheme-state "Otherwise, if url is special, set state to special authority slashes state." -> https://url.spec.whatwg.org/#special-authority-slashes-state "Otherwise, syntax violation, set state to special authority ignore slashes state, and decrease pointer by one." -> https://url.spec.whatwg.org/#special-authority-ignore-slashes-state "If c is neither "/" nor "\", set state to authority state, and decrease pointer by one." -> https://url.spec.whatwg.org/#authority-state "Otherwise, append c to buffer." ...etc; it will parse successfully and up with the same URL record as for ws://example.org/ 1194709 5 zcorpan 2016-05-19 02:36:22 -0700 w-p-t test at http://w3c-test.org/websockets/constructor/017.html