On 14 July 2016 at 17:38, Thiago Macieira wrote:
> On quinta-feira, 14 de julho de 2016 18:33:37 PDT Ben Cooksley wrote:
>
> > Unfortunately, from it's first iteration in Qt 4 QNetworkAccessManager
> > w
> e
> as shipped with a severe and fundamental defect in that it does not
> > follow HTTP
On quinta-feira, 14 de julho de 2016 18:33:37 PDT Ben Cooksley wrote:
> Hi all,
>
> Just my regular reminder regarding usage of QNetworkAccessManager in
> your applications and libraries, especially when it comes to
> interacting with kde.org infrastructure.
>
> Unfortuna
Am Donnerstag, 14. Juli 2016, 12:50:11 CEST schrieb David Faure:
> On jeudi 14 juillet 2016 18:33:37 CEST Ben Cooksley wrote:
> > Please therefore ensure your application handles redirects
> > appropriately (the form of the code will depend on the version of Qt
> > in use) if you decide to use QNAM
On jeudi 14 juillet 2016 18:33:37 CEST Ben Cooksley wrote:
> Please therefore ensure your application handles redirects
> appropriately (the form of the code will depend on the version of Qt
> in use) if you decide to use QNAM.
As an example,
https://lxr.kde.org/source/playground/sdk/inqlude-clie
Hi all,
Just my regular reminder regarding usage of QNetworkAccessManager in
your applications and libraries, especially when it comes to
interacting with kde.org infrastructure.
Unfortunately, from it's first iteration in Qt 4 QNetworkAccessManager
was shipped with a severe and fundam
