Hey,
> hi. apologies if this is a FAQ.
It's not :)
> i occasionally see weird behavior that is *NOT* qutebrowser's fault.
> but, to debug what is going on with some site, i think it would be
> helpful to look at what qutebrowser (or whatever is running under it)
> has in its cache of SSL
Florian,
> 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
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
