[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-bugs-dist
Subject:    [Bug 62425] Lowercasing/normalising URLs breaks some non-compliant
From:       "Petter E.Stokke" <gibreel () gibreel ! net>
Date:       2003-11-05 23:03:03
[Download RAW message or body]

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
     
http://bugs.kde.org/show_bug.cgi?id=62425     




------- Additional Comments From gibreel@gibreel.net  2003-11-06 00:03 -------
Look at these URLs (all of which are correctly parsed by KURL today):

aim:goim?screenname=Foobar&message=Hello+world
magnet:?xt=urn:sha1:PIXQRS5AZHRIXCBEJJS3W2JATUQ6XZZA&dn=foobar.zip
file:/foo/bar/baz?foo=bar

Assuming none of those protocols have a URIMode tag in their respective protocol \
files (file doesn't, and KDE doesn't even handle the other two), they would all be \
parsed as RawURI according to the method you suggest, which means KURL::queryItem() \
et al wouldn't work on them as expected, and, in the case of the file URL especially, \
KURL::path() would be unusable. RawURI doesn't parse anything besides putting \
whatever comes after the colon into m_strPath after expanding %xx constructs, which \
is clearly not what we want in these cases. It should be reserved for protocols which \
are explicitly known to be broken.


[prev in list] [next in list] [prev in thread] [next in thread]