80172 2012-03-02 10:38:37 -0800 [Chromium] KURL behaves differently 2013-04-15 06:26:59 -0700 1 1 1 Unclassified WebKit WebKit Misc. 528+ (Nightly build) Unspecified Unspecified RESOLVED WONTFIX P2 Normal --- 76198 1 toyoshim webkit-unassigned ap bashi brettw ian schenney yutak oldest_to_newest 569757 0 toyoshim 2012-03-02 10:38:37 -0800 WebSocket uses KURL to validate URL. But, KURL in Chromium using googleurl behaves differently from Safari. http://samples.msdn.microsoft.com/ietestcenter/#websockets The white space (%20) is handled as is in Safari, and escaped like '%20' in Chrome. [Safari] > ws = new WebSocket('ws://foo bar/') x Invalid url for WebSocket ws://foo bar x |> DOMException [Chrome] > ws = new WebSocket('ws://foo bar/') |> WebSocket > ws.url "ws://foo%20bar/" We just verity the url as m_url = KURL(KURL(), url); if (!m_url.isValid()) { ... 573988 1 toyoshim 2012-03-08 11:19:12 -0800 I chat about this issue with Brett. >Brett, Sorry, I said that I tried url containing space in path, but actually i tried space in host. Anyway, this escape is intended in Chromium port. So, if WebSocket requires additional error check, we should implement own checker. I filed another bug to introduce WebSocket own URL validator. https://bugs.webkit.org/show_bug.cgi?id=80616