<[EMAIL PROTECTED]> wrote: > I have a config file that is as follows: > > # Extended Log File Format: > # > S-IP\tC-IP\tDATE\tTIME\tCS-METHOD\tCS-URI-STEM\tCS-QUERY\tSC-STATUS\t > TIME-TAKEN\tBYTES > > I have found a line in a http log file as such: > > 155.125.126.156:7101 155.125.14.236 2002-03-18 17:04:55 POST > /Edit/HomeCSS.jsp - 400 1.01648909E9 994 > > > Notice the 9th field is the time-taken field. Most of the time I > have no problem with this field but in this case notice the #.####E9 > format. Using the first LOGFORMAT line with just %t produces this > data line as an error. Yet if I include the second LOGFORMAT line > with it as %tE%j (throw away the E and the value with it) it works. > Is this a bug? Shouldn't a numeric field recognize exponential data?
There is no formal definition of the Extended Log format. There is a W3C Working draft dating from 1996 that provides the essentials, and it specifies that time-taken is of type fixed. time-taken Time taken for transaction to complete in seconds, field has type <fixed> http://www.w3.org/TR/WD-logfile.html Other servers, such as Microsoft IIS, record time-taken in milliseconds as an integer, rather than seconds, which is why Analog supports %t and %T. Even if the first is recorded in milliseconds, 1.01648909E9 seems like an exceptionally long time. Aengus +------------------------------------------------------------------------ | This is the analog-help mailing list. To unsubscribe from this | mailing list, go to | http://lists.isite.net/listgate/analog-help/unsubscribe.html | | List archives are available at | http://www.mail-archive.com/[email protected]/ | http://lists.isite.net/listgate/analog-help/archives/ | http://www.tallylist.com/archives/index.cfm/mlist.7 +------------------------------------------------------------------------
