>> Even so, the "body" content might still be of different sizes, so the >> total bytes will have to change across redirects. This to me doesn't >> look very consistent. > > I say once again: the downloadProgress includes *only* the body, not a single > byte of header or of overhead. Also, downloadProgress() emitting implies > readyRead() also emitted, which means bytes to be read are available. That > only happens once we're at the final body.
Okay. I think Richard also suggested the same approach, i.e as long as we are being redirected, we don't emit the downloadProgress (and other signals indicating there is data available) and do it only once we arrive at the final url (though we continue to read the full response of each redirect). So the final signals will reflect the data as if the request was made directly to that url. Is that your understanding too? -mandeep > > -- > Thiago Macieira - thiago.macieira (AT) intel.com > Software Architect - Intel Open Source Technology Center > > _______________________________________________ > Development mailing list > Development@qt-project.org > http://lists.qt-project.org/mailman/listinfo/development > _______________________________________________ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development