These log files are not properly formatted. You can use them by
specifying custom log formats using the LOGFORMAT command in your
analog.cfg (see http://analog.cx/docs/logfmt.html for details).

However, you should contact your hosting company and submit a bug
report to them and/or the server that's generating these files because
they should be fixed to comply with the spec. The cs-uri-stem field
should have a '-' if there is no data for it and obviously the headers
should be named right.

I suspect (but it's pure speculation) that these files are actually
generated by your hosting company with a script they created
internally after parsing the web server logs. So I think they may have
control of the source and be able to fix this rather quickly.


-- 

Jeremy Wadsack
Wadsack-Allen Digital Group


Peter Greene <[EMAIL PROTECTED]> (Wednesday, March 31, 2004 7:54 AM):

> Can anyone help with (a probably simple?) problem. My hosting company has
> recently changed my logfiles to a W3C extended format logfile with the
> fields heading as follows:

> #Fields: date time s-competername s-ip s-sitename cs-method cs-uri-stem
> cs-uri-query s-port cs-username c-ip cs-version sc-status sc-bytes
> time-taken

> Now here is an example of a single entry from my logfiles:

> 2004-03-30 00:36:09 www.le-marche.com - - GET /Marche/assets/images/Art.gif
> 80 - 159.153.4.50 HTTP/1.1 200 8346 0

> The problem seems to be with the two fields "cs-uri-stem" and "cs-uri-query"
> in the header. If I try and run these logfile through Analog (v.5.32 on
> WinXP) it reckons all lines are corrupt *except* for the tiny number of
> pages that in fact have a ?query at the end of the URI. As you can see in
> the example line above there is no ?query between the "cs-uri-stem" and the
> "s-port" fields.

> If I edit the logfile itself to delete the "cs-uri-query" from the header,
> Analog reads the file ok - *except* for those few pages which have a ?query
> in the line. But clearly having to edit the actual logfiles is a bit silly.

> Can I configure Analog to deal with this problem or does, as I suspect, the
> problem lie with the way the server generates logfiles - I notice that W3C
> guidelines seem to suggest that empty fields in an entry in a logfile should
> have a "-" rather than just being left blank.

> By the way that "competername" in the header is not my mistake!

> Thanks in advance to any public-spirited persons who ris to the challenge.

> Peter Greene

> +------------------------------------------------------------------------
> |  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
> +------------------------------------------------------------------------

+------------------------------------------------------------------------
|  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