eric ide


Author: The Compiler
Recipients: The Compiler, detlev
Date: 2020-05-02.16:34:19
I didn't have a fix ready when I opened the issue, as I first checked how other 
QtWebEngine projects handle this case - turns out only very few handle it 
correctly :)

I don't think there's a way to get the information via JS. The only approaches 
I have found are:

- Open a second connection via QSslSocket to check the certificate:
- Save a set of insecure hosts in the certificateError signals, and assume 
those are always insecure until a restart (what Viper Browser does:

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. Will post a link in a separate post, because I'm not allowed to post 
more than two links...
Date User Action Args
2020-05-02 16:34:19The Compilersetrecipients: + The Compiler, detlev
2020-05-02 16:34:19The Compilersetmessageid: <>
2020-05-02 16:34:19The Compilerlinkissue328 messages
2020-05-02 16:34:19The Compilercreate