Re: Meaning and interpretation of 206 code sizes in Apache logs

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Chris 'Xenon' Hanson wrote:
>   1. Is HE.net making a mistake in using access_log to count bandwidth?
>    1a. What would be the right way to do it?
>    1b. Are they doing it this way because they're using some existing
> tool that does it this way?
>    1c. Are other hosts doing it this way, and therefore are mistakenly
> over-measuring and over-charging customers?

See mod_logio, and there is no affirmative means to know that the client
stuck around to receive every last byte was sent.  That is not covered
by the HTTP protocol, but mod_logio attempts to look deeper (and adds
additional overhead) to make the best determination that it can.

>   2. What exactly does the number after the 206 code in the access_log
> mean? Is it simply the range the client _requested_ via the Range
> header? In which case, it has no real relationship to how much data was
> _actually_ transferred?

206 is no different than 200.  In both cases the client might not actually
receive the entire requested range.

---------------------------------------------------------------------
The official User-To-User support forum of the Apache HTTP Server Project.
See <URL:http://httpd.apache.org/userslist.html> for more info.
To unsubscribe, e-mail: users-unsubscribe@xxxxxxxxxxxxxxxx
   "   from the digest: users-digest-unsubscribe@xxxxxxxxxxxxxxxx
For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx


[Index of Archives]     [Open SSH Users]     [Linux ACPI]     [Linux Kernel]     [Linux Laptop]     [Kernel Newbies]     [Security]     [Netfilter]     [Bugtraq]     [Squid]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Samba]     [Video 4 Linux]     [Device Mapper]

  Powered by Linux