[Webkit-unassigned] [Bug 80172] New: [Chromium] KURL behaves differently

[bugzilla-daemon at webkit.org]

https://bugs.webkit.org/show_bug.cgi?id=80172

           Summary: [Chromium] KURL behaves differently
           Product: WebKit
           Version: 528+ (Nightly build)
          Platform: Unspecified
        OS/Version: Unspecified
            Status: NEW
          Severity: Normal
          Priority: P2
         Component: WebKit Misc.
        AssignedTo: webkit-unassigned at lists.webkit.org
        ReportedBy: toyoshim at chromium.org
                CC: ian at hixie.ch, brettw at chromium.org, yutak at chromium.org,
                    bashi at chromium.org


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()) {
  ...

-- 
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.