On 01/12/2014, at 8:43 AM, Thomas Lübking wrote: > On Sonntag, 30. November 2014 15:37:22 CEST, Andrea Iacovitti wrote: > >> If i understand well the problem and the goal is to disable the use of >> cookies, may be it could be achieved by using kio METADATA (see doc >> file kdelibs/kio/DESIGN.metadata). >> E.g. job->addMetaData("cookies", "none") should disable the use of >> cookies for that job. > > Cool, didn't know that =) > > "Unfortunately" DrKonqi currently uses sync static KIO::NetAccess::upload(), > so the patch would require to move to KIO::copy() and either turn the entire > thing async (and disable the UI ;-) or add a custom nested eventloop.
And I think it does whatever it does from inside KXmlRpc::Client, a kdelibs4 class (frozen). > I assume we've to pick the least invasive solution (make 4,4,6 use password > security) - for SC4, at least. Agreed. Also a solution that can be released, given current KDE SC 4 release policies. When/if Dr K is redesigned/reorganised for KF5, David Faure has suggested using QtWebKit and QNetworkAccessManager. See the "DrKonqi placement" thread. Cheers, Ian W.