[Development] [API Change] New authentication method in QNetworkAccessManager

Richard Moore rich at kde.org
Sun Mar 9 22:46:40 CET 2014


On 9 March 2014 20:13, Kurt Pattyn <pattyn.kurt at gmail.com> wrote:

>
> On 09 Mar 2014, at 21:02, Giuseppe D'Angelo <dangelog at gmail.com> wrote:
>
> > On 9 March 2014 15:10, Kurt Pattyn <pattyn.kurt at gmail.com> wrote:
> >> Also, the connection between the authenticationRequired signal and the
> slot
> >> must be a direct connection.
> >
> > IIRC SSL sockets had the same "issue" when SSL errors are raised. Has
> > it been solved there? How?
> AFAIK, it has not been solved. The problem is the same.
>

It has been partially solved, in recent versions you can set the socket to
pause when ssl errors occur which avoids the need to use a nested event
loop, see https://codereview.qt-project.org/#change,13834 We want this to
be supported for authentication and also for ssl when there are no errors.
It is being tracked as
QTBUG-19032<https://bugreports.qt-project.org/browse/QTBUG-19032>
.

Rich.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.qt-project.org/pipermail/development/attachments/20140309/fd4928d3/attachment.html>


More information about the Development mailing list