I discovered that analog also counts as corrupt lines that have a the
request field with a blank in the url.
Example:
206.172.104.8 - - [30/Jun/1999:19:26:32 -0700] "GET /~myoung/Copy of
sm_xr250.jpg HTTP/1.0" 404 3464 ....
is counted as a corrupt line, but if I change
Copy of sm_xr250.jpg
to
Copyofsm_xr250.jpg
in my logfile, then it is not counted as corrupt.
Any way to fix or work around this?
Thanks.
-----Original Message-----
From: James H. Thompson <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED] <[EMAIL PROTECTED]>
Date: Thursday, July 01, 1999 8:54 PM
Subject: [analog-help] Corrupt log file lines
>Analog is working fine except that I'm getting periodic
>corrupt logfile lines. Example: on a log file of about 700K lines I get:
>
> Corrupt logfile lines: 708
>
>I tracked it to a line that appears in the logfile of:
>
>170.38.99.105 - - [30/Jun/1999:00:26:21 -0700] "-" 408 - www.off-road.com
>"-" "-" "-"
>
>>From the HTTP 1.1 RFC: an "408" status code is a Request Time-out
>
>I'm using:
>ApachedefaultLogFormat (%h %l %{junk}i %t \"%r\" %s %b %v \"%{Referer}i\"
>\"%{User-agent}i\" \"%u\")
>
>Line doen't seem corrupt?
>
>It would be nice to have an analog option to direct corrupt log file lines
>to a file for later analysis.
>
>Thanks.
>
>Jim
>
>
>------------------------------------------------------------------------
>This is the analog-help mailing list. To unsubscribe from this
>mailing list, send mail to [EMAIL PROTECTED]
>with "unsubscribe analog-help" in the main BODY OF THE MESSAGE.
>List archived at http://www.mail-archive.com/[email protected]/
>------------------------------------------------------------------------
>
------------------------------------------------------------------------
This is the analog-help mailing list. To unsubscribe from this
mailing list, send mail to [EMAIL PROTECTED]
with "unsubscribe analog-help" in the main BODY OF THE MESSAGE.
List archived at http://www.mail-archive.com/[email protected]/
------------------------------------------------------------------------
