-
Notifications
You must be signed in to change notification settings - Fork 669
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Restore sll error behaviour #9678
Conversation
Results for GUI-tests https://drone.owncloud.com/owncloud/client/11785/6/1 💥 The GUI tests failed. GUI Logs: https://cache.owncloud.com/public/owncloud/client/11785/guiReportUpload/index.html |
4835293
to
d493537
Compare
This matches the old behaviour
d493537
to
4cc418c
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good. I'm not a fan of the old behavior, though. Is the idea of storing the error along with the certificate still something we want to realize (even if just long-term)?
@@ -40,6 +42,16 @@ AccessManager::AccessManager(QObject *parent) | |||
setConfiguration(QNetworkConfiguration()); | |||
#endif | |||
setCookieJar(new CookieJar); | |||
|
|||
connect(this, &AccessManager::sslErrors, this, [this](QNetworkReply *reply, const QList<QSslError> &errors) { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can we make sure this slot is run first using some flag on connect
?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thinking about it, maybe we should just debug log all erased errors. That way, whoever will work with this code in the future, will get notified about ignored errors.
Kudos, SonarCloud Quality Gate passed! |
Please open an issue for 4.0 |
No description provided.