Remove HTTP 1XX status test from tst_qrestaccessmanager
1XX statuses are not final statuses, and testing 'error' on it is not necessarily very meaningful. Furthermore the internal handling of these statuses changes in Qt 6.8. Fixes: QTBUG-108068 Pick-to: 6.7 Change-Id: I9c18c579cd310266273eccd2aee2e032f60538e0 Reviewed-by: Mårten Nordheim <marten.nordheim@qt.io>
This commit is contained in:
parent
bb34c6fa6b
commit
cdfeca26cf
@ -478,7 +478,6 @@ void tst_QRestAccessManager::errors()
|
|||||||
});
|
});
|
||||||
|
|
||||||
// Test few HTTP statuses in different categories
|
// Test few HTTP statuses in different categories
|
||||||
VERIFY_HTTP_ERROR_STATUS(103) // QNetworkReply::NoError
|
|
||||||
VERIFY_HTTP_ERROR_STATUS(301) // QNetworkReply::ProtocolUnknownError
|
VERIFY_HTTP_ERROR_STATUS(301) // QNetworkReply::ProtocolUnknownError
|
||||||
VERIFY_HTTP_ERROR_STATUS(302) // QNetworkReply::ProtocolUnknownError
|
VERIFY_HTTP_ERROR_STATUS(302) // QNetworkReply::ProtocolUnknownError
|
||||||
VERIFY_HTTP_ERROR_STATUS(400) // QNetworkReply::ProtocolInvalidOperationError
|
VERIFY_HTTP_ERROR_STATUS(400) // QNetworkReply::ProtocolInvalidOperationError
|
||||||
|
Loading…
x
Reference in New Issue
Block a user