On Sunday, April 24, 2005 7:47 PM [GMT],
Emil Pedersen <[EMAIL PROTECTED]> wrote:

>>>> The Apache bug you reference is what you might reasonably call an
>>>> exception - if aborted transfers make up a significant proportion
>>>> of
>>>
>>> Unfortunately it does.  Just for a test, I tried to exclude lines
>>> with partial requests (code 206), and the two reports differed
>>> enourmously. IIRC  the one with part.reqs. included was about 30
>>> times as big as the other, which was more in line with what was
>>> excpected.
>>
>> 206's are NOT aborted transfers. They are partial transfers. If you
>
> Sure, but an aborted transfer will likely generate an imediate partial
> request.

An aborted transfer will generate a 200 status code. The server doesn't
care that the client decided not to complete the transfer, it is a
"success" from the servers point of view. But it's not a "partial
request". A single user reading a single 10 page PDF document on your
website can generate 10 206 "partial requests" in your log. They won't
generate 10 aborted transfers of that file. 206 requests do pose certain
difficulties for some people when it comes to understanding their sites
traffic problems, but they cause a problem precisely because they aren't
"interrupted requests" - many people who encounter difficulty in
counting 206s would actually prefer if there was just a single request,
aborted after downloading 4 of the pages, if necessary, rather than
multiple requests that make it difficult to measure how many "hits" they
actually have against specific documents.

(It's just not an issue for most people, but it tends to be a real pain
for anyone who doesn't care about it).

Aengus


+------------------------------------------------------------------------
|  TO UNSUBSCRIBE from this list:
|    http://lists.meer.net/mailman/listinfo/analog-help
|
|  Usenet version: news://news.gmane.org/gmane.comp.web.analog.general
|  List archives:  http://www.analog.cx/docs/mailing.html#listarchives
+------------------------------------------------------------------------

Reply via email to