https://bugs.kde.org/show_bug.cgi?id=471851
fanzhuyi...@gmail.com changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|--- |INTENTIONAL
Status|CONFIRMED |RESOLVED
--- Comment #3 from fanzhuyi...@gmail.com ---
After some research, I am closing this as INTENTIONAL.
Short answer:
Don't add the double slashes for custom schemes.
Just use custom-scheme:xxxxx, instead of custom-scheme://xxxxxx.
Long answer:
With the double slashes, the part that comes after will be interpreted as a
host.
As per specifications, the host cannot have more than 63 characters.
So QUrl::fromUserInput perceives this to be an invalid url, and tries to fix
this.
The 'fixed' url becomes http://custom-scheme//xxxxxxx.
On the other hand, if the double slashes are not included,
then what comes after becomes interpreted as the path, which does not have the
63 character limit. So QUrl::fromUserInput treats it as valid url and doesn't
modify it.
References:
https://en.wikipedia.org/wiki/Uniform_Resource_Identifier
https://en.wikipedia.org/wiki/Hostname#Restrictions_on_valid_host_names
https://bugreports.qt.io/browse/QTBUG-18280
--
You are receiving this mail because:
You are watching all bug changes.
