-----BEGIN PGP SIGNED MESSAGE-----
On 04/30/2009 02:40 AM, Axel Thimm wrote:
On Wed, Apr 29, 2009 at 09:09:27PM +0800, Basil Mohamed Gohar wrote:
> On 04/29/2009 08:20 PM, Axel Thimm wrote:
>> On Tue, Apr 28, 2009 at 11:17:55AM -0400, Paul W. Frields wrote:
>>>> Maybe the cleanest solution is to count downloaded bytes and divide by
>>>> image size. That way you properly count ranged downloads.
>>> Command suggestions are very welcome. I really don't have time to
>>> delve into this incredibly deeply at the moment.
>> Could you post a small fragment of the raw logs? But it seems like all
>> we see are the primary redirects, possibly w/o noting ranges in the
>> logs. E.g. for better statistics the logs would need to capture the
>> ranges from the head as well.
> I think that information is not available, because no one (almost)
> downloads directly from the Fedora servers, only from the mirrors.
> Therefore, the real data, like range requests, etc., would only be on
> the mirror servers themselves, and not on the primary ones.
Isn't a range request sent in the header of the HTTP request which
would hit the Fedora servers before being redirected?
Not if the range request was after being redirected. I think, in the
same download, the redirect is only processed once, even if it is a
temporary one. Therefore, unless the first request was a partial
content one, then the connection has already been redirected to the
mirror server, and thus the main Fedora server will not see it.
I'd draw a diagram, but I'm terrible at doing so.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org/
-----END PGP SIGNATURE-----