https://bugs.kde.org/show_bug.cgi?id=420902
--- Comment #1 from Florian Bruhin <[email protected]> --- I've looked at how other projects using QtWebEngine handle this case. The only approaches I have found are: - Open a second connection via QSslSocket to check the certificate: https://github.com/vicr123/theweb/commit/5f6cbc6093a1adb4fdf3db829b182139e065319b - Save a set of insecure hosts in the certificateError signals, and assume those are always insecure until a restart, from Viper Browser: https://github.com/LeFroid/Viper-Browser/blob/master/src/core/network/SecurityManager.cpp I decided to go for the latter with qutebrowser - I already did set a flag in this situation so the UI was correct for the first load, but not for subsequent loads. The preliminary qutebrowser fix (currently waiting for CI) is here: https://github.com/qutebrowser/qutebrowser/commit/c7a0a150b2e991cc1c2fe8b883b074a800c2c40e -- You are receiving this mail because: You are watching all bug changes.
