dantti added a comment.
Well the issue will probably depend on the server, for example Apache2 with Nextcloud it returns forbidden for both operations, in Cloudlyst which does: QUrl::fromEncoded(QStringLiteral("file:///speçiál").toLatin1()).toLocalFile(); you get a file with a different file name as URL. Since 'ç' is extended ASCII this "fails" only because URL are sopposed to use only printable ASCII chars If you use some some UTF-8 char like ←it wil produce that behavior: QStringLiteral("spe←ail\r\n").toLatin1() will produce: "spe?ail\r\n" and the question mark is interpreted as being the query part of an URL, thus what I said before that it cuts everything past the special char due URL parsing. you can see doing this: QUrl::fromEncoded(QStringLiteral("file:///file←sadssad").toLatin1()).toLocalFile() local file will be "/file" REPOSITORY R241 KIO REVISION DETAIL https://phabricator.kde.org/D14006 To: dantti, dfaure, #frameworks, #dolphin Cc: bruns, anthonyfieroni, ngraham, kde-frameworks-devel, michaelh