according to the KIO::ERR_COULD_NOT_AUTHENTICATE error description it is
used when the authentication method is not supported, not when credentials
are required or incorrect
Signed-off-by: Ivailo Monev <xakepa10@gmail.com>
note that KIO::ERR_SERVICE_NOT_AVAILABLE was not handled in
KIO::buildErrorString() (since before the fork)
Signed-off-by: Ivailo Monev <xakepa10@gmail.com>
with klauncher no longer responsible for KIO slave the next step is to
make them plugins and the feature to put them on hold will be of no value
because QLibrary reuses library/plugin instances and creating a new
slave object will be cheap
in other words the performance will be similar to that of KFileMetaInfo
for which I also wrote the plugins myself - they are pretty quick
compared to what strigi was doing and with more flexible configuration
interface but it took some effort to get there
Signed-off-by: Ivailo Monev <xakepa10@gmail.com>
most of the refactoring is so that headers are parsed and error is emited
if HTTP status is >= 400 before MIME type is emited from the slave
Signed-off-by: Ivailo Monev <xakepa10@gmail.com>
fixes state of transfers done via KIO plugin in KGet (the transfers state
was set to stalled even while download is in progress)
Signed-off-by: Ivailo Monev <xakepa10@gmail.com>
it goes like this:
Received 0 from 0
Received 0 from 0
Received 0 from 0
Received 0 from 0
Received 0 from 0
Received 0 from 0
Received 0 from 0
Received 0 from 0
Received 0 from 0
Received 0 from 0
Received 0 from 0
Received 0 from 0
Received 0 from 0
Received 0 from 0
Received 0 from 0
Received 0 from 0
Received 0 from 0
Received 0 from 0
Received 0 from 0
Received 0 from 0
Received 663 from 663
Received 663 from 663
Received 663 from 663
Received 0 from 0
Received 0 from 0
Received 0 from 0
Received 0 from 0
Received 0 from 0
Received 0 from 0
Received 0 from 0
Received 0 from 0
Received 0 from 0
Received 0 from 0
Received 0 from 0
Received 0 from 0
Received 0 from 0
Received 0 from 0
Received 0 from 0
Received 0 from 0
Received 9134 from 8869796
Received 9134 from 8869796
Received 10512 from 8869796
Received 10512 from 8869796
Received 11890 from 8869796
Received 11890 from 8869796
Received 14646 from 8869796
Received 14646 from 8869796
Received 15583 from 8869796
Received 15583 from 8869796
Received 16952 from 8869796
Received 16952 from 8869796
Received 19708 from 8869796
Received 19708 from 8869796
Received 21086 from 8869796
Received 21086 from 8869796
Received 23842 from 8869796
Received 23842 from 8869796
Received 26598 from 8869796
Received 26598 from 8869796
Received 29354 from 8869796
Received 29354 from 8869796
Received 31967 from 8869796
...
it could be curl giving progress on redirects, could be servers sending
bogus content length, idk but it's not a bug that needs fixing here
(the output is from GitHub transfer)
Signed-off-by: Ivailo Monev <xakepa10@gmail.com>