27.02.2018, 18:39, "coroberti ." <corobe...@gmail.com>: > Hi Tomek, > It was a similar case in my setup. > > It appeared, though, that I was 2 connections and deleting the first > conn before getting reply. > > If you are using the same connection, check that your server supports > pipe-lining. > You need somehow to manage QNetworkReply/s - perhaps 2 different objects.
Pipelining may be used only when QNetworkRequest::HttpPipeliningAllowedAttribute is set to true > > Kind regards, > Robert > > On Tue, Feb 27, 2018 at 10:44 AM, Tomasz Olszak <olszak.tom...@gmail.com> > wrote: >> Hello, >> >> I faced strange issue.Probably important information" >> 1. I send 2 GET request in short delay between them (a few ms). Request have >> the same URL (including GET variables). They are connecting to remote HTTPS >> nginx server >> 2. I save both replies from QNAM in internal cache and when the latter reply >> is finished I print information about first one. First one is running, not >> finished, no error. There is no signal emitted from first reply (like >> encrypted, metadataChanged etc), those signal are emitted from second reply >> though. >> >> Anyone has an idea what could happen and how to debug it? >> >> Thanks in Advance, >> Tomek >> >> _______________________________________________ >> Interest mailing list >> Interest@qt-project.org >> http://lists.qt-project.org/mailman/listinfo/interest > > _______________________________________________ > Interest mailing list > Interest@qt-project.org > http://lists.qt-project.org/mailman/listinfo/interest -- Regards, Konstantin _______________________________________________ Interest mailing list Interest@qt-project.org http://lists.qt-project.org/mailman/listinfo/interest
