https://bugs.kde.org/show_bug.cgi?id=429408
André Werlang <bepp...@gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |bepp...@gmail.com
--- Comment #19 from André Werlang <bepp...@gmail.com> ---
(In reply to Connor Schunk from comment #6)
> In QUrl (https://code.woboq.org/qt5/qtbase/src/corelib/io/qurl.cpp.html), I
> notice "nameprepping" and RFCs related to normalization are mentioned a few
> times, e.g.
> > Note that the case folding rules in \l{RFC 3491}{Nameprep}, which QUrl
> > conforms to, require host names to always be converted to lower case,
> > regardless of the Qt::FormattingOptions used
Except RFC 3491 doesn't make any mention to "case folding". RFC 3490 mentions
> 4) Whenever two labels are compared, they MUST be considered to match
> if and only if they are equivalent, that is, their ASCII forms
> (obtained by applying ToASCII) match using a case-insensitive
> ASCII comparison. Whenever two names are compared, they MUST be
> considered to match if and only if their corresponding labels
> match, regardless of whether the names use the same forms of label
> separators.
I don't think this applies to QUrl as no comparison between labels takes place.
(In reply to Oded Arbel from comment #10)
> I believe the correct RFC for QURL implementations - in this case - is RFC
> 3986: URI Generic Syntax, where section 3.2.2 says: "The host subcomponent
> is case-insensitive". Granted that a reading of the spec to mean "fold
> everything to lowercase" is reaching a bit, but as per RFC 1122, p1.2.2 -
> receivers should accept lowercased host names.
It's not reaching a bit, RFC recommends lowercasing domain names in section
3.2.2:
> Although host is case-insensitive, producers and normalizers should use
> lowercase for registered names and hexadecimal addresses for the sake of
> uniformity, while only using uppercase letters for percent-encodings.
Keyword here is SHOULD. QUrl is not _required_ to do so.
TLDR; Thunderbird should avoid the authority component and use a single "/"
character or none at all after the ":". kde-open5 probably doesn't need to
normalize anything just to figure out the correct scheme handler.
--
You are receiving this mail because:
You are watching all bug changes.
