[Development] Proposal for allowing handling of HTTP redirects in QNAM

Thiago Macieira thiago.macieira at intel.com
Sat Dec 28 23:27:33 CET 2013

On quinta-feira, 26 de dezembro de 2013 22:39:03, Mandeep Sandhu wrote:
> > There is no downloadProgress for any intermediate requests. We know that
> > we're redirecting before we get the first byte of data out of the server.
> > At that point, we can abandon the QHttpNetworkReply and move on to the
> > next already.
> The downloadProgress signal gives info about the received & total
> bytes for a n/w request. The total bytes, I think, also include the
> bytes used up by the HTTP headers.

No, it doesn't. It includes only data. The HTTP headers are metadata, so they 
don't count.

> So this might change from 1 redirect to another based on what headers
> the server returns. So my total bytes for the first request might X,
> while for the next request it might be something different. So even if
> we don't consider the intermediate requests, what should these 2
> parameters indicate? only data about the 1st request?
> I don't see a clean way of having a single downloadProgress signal
> encompassing all the intermediate requests.

Thiago Macieira - thiago.macieira (AT) intel.com
  Software Architect - Intel Open Source Technology Center
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 190 bytes
Desc: This is a digitally signed message part.
URL: <http://lists.qt-project.org/pipermail/development/attachments/20131228/1c1154fe/attachment.sig>

More information about the Development mailing list