Hi Luca, On 09/30/2013 11:45 AM, Luca Ottaviano wrote:
Hi Alberto, I would say that's an error on the certificate side and you should strive to use a proper certificate chain, so that you don't have any failures. There are many subtleties that can destroy the security of your application. [1]
Absolutely. I need this only in some test code, where I'm verifying my component against a local web server, which uses a self-signed certificate.
That said, I guess your only option in QML WebKit 3.0 is to use the experimental features. Every component you set to experimental.certificateVerificationDialog is given a model with the following properties and methods: * model.hostname: the hostname that triggered the ssl error * model.accept(): call this if you want to ignore the error * model.reject(): call this if you want to stop loading the page You can only extract further info by reading the source code of qtwebkit and by checking the test cases. See for example: Source/WebKit2/UIProcess/API/qt/qquickwebview.cpp Source/WebKit2/UIProcess/API/qt/qquickwebview_p.h
Cool! Thank you very much!! Ciao, Alberto _______________________________________________ webkit-qt mailing list [email protected] https://lists.webkit.org/mailman/listinfo/webkit-qt
