Thiago Macieira 4d79312f1c Ensure proper handling of empty-but-present URL components ... The new QUrl is able to distinguish a URL component that is empty from one that is absent. The previous one already had that capability for the port, fragment and query, and the new one extends that to the username, password and path. The path did not need this handling because its delimiter from the authority it part of the path. For example, a URL with no username is one where it's set to QString() (null). A URL like "http://:kde@kde.org" is understood as an empty-but-present username, for which toString(RemovePassword) will return "http://@kde.org", keeping the empty-but-present username. Change-Id: I2d97a7656f3f1099e3cf400b199e68e4c480d924 Reviewed-by: Shane Kearns <shane.kearns@accenture.com>		2012-04-12 23:01:37 +02:00
..
.gitignore	Moving relevant tests to corelib/io	2011-08-31 10:08:38 +02:00
idna-test.c	Remove "All rights reserved" line from license headers.	2012-01-30 03:54:59 +01:00
qurl.pro	Mark QUrl::{to,from}Punycode as deprecated since 5.0	2012-03-30 01:19:59 +02:00
tst_qurl.cpp	Ensure proper handling of empty-but-present URL components	2012-04-12 23:01:37 +02:00