hi. apologies if this is a FAQ. 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 certificates. added niceness would be to be able to clear an entry from the cache.
any ideas? cheers, Greg here's my system: ---- qutebrowser v2.5.4 Git commit: Backend: QtWebEngine 5.15.13, based on Chromium 87.0.4280.144 Qt: 5.15.9 (compiled 5.15.8) CPython: 3.11.3 PyQt: 5.15.9 sip: 6.7.9 colorama: 0.4.6 jinja2: 3.1.2 pygments: 2.15.1 yaml: 6.0 adblock: 0.6.0 PyQt5.QtWebEngineWidgets: yes PyQt5.QtWebEngine: 5.15.6 PyQt5.QtWebKitWidgets: no pdf.js: 3.6.172 (/usr/share/pdf.js/build/pdf.js) sqlite: 3.42.0 QtNetwork SSL: OpenSSL 3.0.8 7 Feb 2023 Style: QFusionStyle Platform plugin: xcb OpenGL: Intel, 4.6 (Compatibility Profile) Mesa 23.0.3 Platform: Linux-6.3.3-arch1-1-x86_64-with-glibc2.37, 64bit Linux distribution: Arch Linux (arch) Frozen: False Imported from /usr/lib/python3.11/site-packages/qutebrowser Using Python from /usr/bin/python3 Qt library executable path: /usr/lib/qt/libexec, data path: /usr/share/qt Paths: cache: /home/minshall/.cache/qutebrowser config: /home/minshall/.config/qutebrowser data: /home/minshall/.local/share/qutebrowser runtime: /run/user/1000/qutebrowser system data: /usr/share/qutebrowser Autoconfig loaded: yes Config.py: /home/minshall/.config/qutebrowser/config.py has been loaded Uptime: 0:00:00
