On Fri, 26 Mar 1999, Jim Foley wrote:
>
> This looks like a combined format. If you are compressing the log
> files and using a uncompress to stdout for analog, you may have
> define COMBINED as your default format. 3.11 appears to not be
> able to read the format automatically in the event that the logfile is
> uncompressed to stdout.
>
Right fix, wrong reason.
Yes, it's combined format, and so specifying LOGFORMAT COMBINED will work.
The reason it doesn't work is that it (correctly) diagnoses it as Netscape
format, but the Netscape log format parser assumes that the request is in
the form "GET /file HTTP/1.0", not just "GET /file" which your requests all
seem to be. The latter is however a vaild request, and LOGFORMAT COMBINED
will accept it.
The reason I haven't made it work is that it's a bit difficult to build all
those possibilities in to a format that varies according to an initial
format line. With the fixed formats like COMBINED, all the legal
possibilities are understood. But HTTP/0.9 requests are so rare nowadays
that I didn't think much was lost by ignoring them in the variable formats.
I was obviously wrong in your case... But one can always specify a LOGFORMAT
if too many good lines are being thrown away.
On to Jim's point, 3.11 certainly auto-diagnoses formats for logfiles it's
uncompressing exactly the same as for any logfile. I've just tested it to
make sure.
--
Stephen Turner [EMAIL PROTECTED] http://www.statslab.cam.ac.uk/~sret1/
Statistical Laboratory, 16 Mill Lane, Cambridge CB2 1SB, England
"Ad infinitum, if not ad nauseam." (Interviewee, BBC Radio 4)
--------------------------------------------------------------------
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.
--------------------------------------------------------------------
