Per Jessen <[EMAIL PROTECTED]> wrote:
> Aengus wrote:
>
>> [EMAIL PROTECTED] wrote:
>>>
>>> U:\ANALOG\analog 5.32>analog
>>> analog: analog version 5.32/Win32
>>> analog: Warning C: Sorry, can't parse "%...{format}t" in
>>>   APACHELOGFORMAT: ignoring whole line
>>
>> Apparently, Analog can't handle that sort of Apache logformat macro.
>>
>> You'll have to wait for someone who is more familiar with Apache to
>> answer this one.
>
> It's not apache that's causing a problem, but analog.

I didn't say it was an Analog problem. I said that someone more familiar
with Apache would have to answer this question.

> Analog does not
> have full support for the Apache log formats, only a subset thereof.
> Analog recognises "%{host}i", "%{referer}i" and "%{user-agent}i", and
> will ignore all the other possible formats, except the "%{format}t",
> which is explicitly rejected.

And I think you just proved my point :-)

2003/11/25 00:00:06 127.0.0.1 - 127.0.0.1 GET
/wdeliver/servlet/JSPs/shop/check.jsp HTTP/1.1 - 200 1858 - 0
"Java1.3.1" "
-" "-"

As you've now confirmed that he can't use the APACHELOGFORMAT command, I
manually put together this LOGFORMAT which handles the log lines
provided in the first message:
LOGFORMAT (%Y/%m/%d %h:%n:%j %S - %j %j %r %j %j %c %b %j"%B" "%u" "%f")

As I am not familiar with the Apache directives, I've just used %j for
anything that's not immediately apparent (I also use %j for the
processing time field, because Apache apparently measures that in whole
seconds, which isn't much use). I used the cookie field for the User
field.

Aengus

+------------------------------------------------------------------------
|  TO UNSUBSCRIBE from this list:
|    http://lists.isite.net/listgate/analog-help/unsubscribe.html
|
|  Digest version: http://lists.isite.net/listgate/analog-help-digest/
|  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