KDav without KIO

[Christian Mollekopf]

On Mon, Jun 26, 2017, at 10:45 AM, Christian Mollekopf wrote:
> On Mon, Jun 26, 2017, at 10:16 AM, Daniel Vrátil wrote:
> > On Sunday, June 25, 2017 5:19:13 PM CEST Christian Mollekopf wrote:

> > 
> > From a quick glance at a code:
> > 
> > Since QWebDav is compeltely internalized to KDavManager, I don't see any
> > way to:
> > 1) handle SSL errors - you don't connect to
> > QWebDav::checkSslCertificate() or 
> > expose the signal through public API, so applications cannot show a
> > dialog to confirm the SSL error, thus you won't be able to use KDAV against servers
> > with e.g. self-signed certificates.
> > 2) configure proxy - previously KIO would handle this automagically, now
> > we need a way to pass QNetworkProxy settings to QWebDav's QNAM.
> > 
> 
> I think our best bet to solve those two is to remove any error handling
> from QWebDav and expose
> the QNetworkAccessManager via some static API.

I have now exposed the QNetworkAccessManager via the DavManager class.
This IMO resolves both issues.