Hey,

> > From what I'm aware, you can:
> > 
> > a) Use :devtools and look at the security tab there
> > b) Use Shift-R (:reload -f) to force a reload
> > c) Go to chrome://net-internals/#hsts to deal with HSTS entries.
> 
> thanks.  you're right, it's not much.  (i'd like to see the intermediate
> certificates provided with the server's main certificate, in order to
> see the chain back up to a CA.)

There is no API for QtWebEngine that would provide this information for
successful loads: https://bugreports.qt.io/browse/QTBUG-80860

There was an API added to get this information when there is a
certificate error displayed. However, that's not implemented in
qutebrowser so far, which is currently tracked here:
https://github.com/qutebrowser/qutebrowser/issues/4616

Florian

Attachment: pgpBiyR6N6QnW.pgp
Description: PGP signature

Reply via email to