Improve iOS https error handling.
Set the reply state to "finished" also on errors. Do a proper string compare to correctly translate the error codes. Task-number: QTBUG-42023 Change-Id: I222cc06a47b1f9f89095e8f935f316bf94fd0cd6 Reviewed-by: Caroline Chao <caroline.chao@theqtcompany.com> Reviewed-by: Richard Moe Gustavsen <richard.gustavsen@digia.com>bb10
parent
2580192def
commit
56bb02ade3
|
|
@ -245,7 +245,7 @@ void QNetworkReplyNSURLConnectionImpl::readyReadOutgoingData()
|
|||
Q_UNUSED(connection)
|
||||
|
||||
QNetworkReply::NetworkError qtError = QNetworkReply::UnknownNetworkError;
|
||||
if ([error domain] == NSURLErrorDomain) {
|
||||
if ([[error domain] isEqualToString:NSURLErrorDomain]) {
|
||||
switch ([error code]) {
|
||||
case NSURLErrorTimedOut: qtError = QNetworkReply::TimeoutError; break;
|
||||
case NSURLErrorUnsupportedURL: qtError = QNetworkReply::ProtocolUnknownError; break;
|
||||
|
|
@ -260,6 +260,7 @@ void QNetworkReplyNSURLConnectionImpl::readyReadOutgoingData()
|
|||
}
|
||||
|
||||
replyprivate->setError(qtError, QString::fromNSString([error localizedDescription]));
|
||||
replyprivate->setFinished();
|
||||
}
|
||||
|
||||
- (void)connection:(NSURLConnection*)connection didReceiveResponse:(NSURLResponse*)aResponse
|
||||
|
|
|
|||
Loading…
Reference in New Issue