[Webkit-unassigned] [Bug 106728] [KURL] 'https:' gets adjusted to 'https:/'

[bugzilla-daemon at webkit.org]

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





--- Comment #5 from Zan Dobersek <zandobersek at gmail.com>  2013-01-16 05:57:13 PST ---
(In reply to comment #4)
> The bug is correct ("https:" is an invalid URL, and we should not attempt to canonicalize it), but the patch is wrong.

Could you please elaborate on 'https:' being an invalid URL?

I'm using RFC 3986 as a base, and that states:

"The scheme and path components are required, though the path may be
empty (no characters).  When authority is present, the path must
either be empty or begin with a slash ("/") character."
http://tools.ietf.org/html/rfc3986#page-16

Basically, 'https:' consists of only a scheme and an empty path.
Am I missing something?

> If you are interested in improving URL parsing, I suggest you to look into WTFURL.

I've looked around a bit about WTFURL, I find it interesting. It seems though it's not currently used by any port, so I'd like to fix this problem in the scope of the old KURL implementation first.

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