[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:       Thiago Macieira <thiagom () mail ! com>
Date:       2003-11-05 22:03:51
[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 thiagom@mail.com  2003-11-05 23:03 -------
That's not what I meant. What I wanted to do is add an extra check for the automatic \
mode, for when KURL doesn't find a value for a given protocol.

The decision would be thus like this:
- if the mode is on cache, use it
- if the .protocol file has the value, use it (and cache)
- if the mode hasn't been detected, look at the URI schema (the protocol)
.- if it's mailto:, set the mode to MailTo mode
.- if it's one of the known broken schemas (ed2k, sig2dat, slsk), use RawURI
and here's the change:
.- if it's still unknown, but the non-schema part starts with //, it's URL
.- otherwise, it's RawURI

What the RFCs say is that anything://something-else is a URL and that's what those \
broken protocols violate (because they have // not followed by a hostname). Other \
schemas may be specified (like data or mailto) with different parsings.


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