Recent changes to patcheshttp://sourceforge.net/p/awstats/patches/2015-07-31T11:35:34Z#213 LogFormat: match literal content2015-07-31T11:35:34Z2015-07-31T11:35:34ZBoštjan Škufcahttp://sourceforge.net/u/bostjanskufca/http://sourceforge.net0577035540f6706d6fe6132971ff658de2f0d068<div class="markdown_content"><p>Here is the pull request:<br />
<a href="https://github.com/teonsystems/awstats/tree/feature/logformat-literal-strings-support" rel="nofollow">https://github.com/teonsystems/awstats/tree/feature/logformat-literal-strings-support</a></p>
<p>Have fun,<br />
b.</p></div>#214 LogFormat: make colon in time zone specification optional2015-07-30T17:33:22Z2015-07-30T17:33:22ZBoštjan Škufcahttp://sourceforge.net/u/bostjanskufca/http://sourceforge.netb5b92f5f5270178f5940fcffd7d5bea44eb22321<div class="markdown_content"><p>Ah crap. After half of hour of regex juggling I figure out that changes in develop branch already contain fix for this :)</p>
<p>Anyway, here is pull request with:<br />
- updated documentation about this<br />
- add support for "Z" only, which completes ISO 8601 support<br />
- make whole timezone part optional, to support the most datetime formats</p>
<p><a href="https://github.com/teonsystems/awstats/tree/enhancement/logformat-iso-tz-updates" rel="nofollow">https://github.com/teonsystems/awstats/tree/enhancement/logformat-iso-tz-updates</a></p>
<p>b.</p></div>#214 LogFormat: make colon in time zone specification optional2015-07-22T11:37:04Z2015-07-22T11:37:04ZBoštjan Škufcahttp://sourceforge.net/u/bostjanskufca/http://sourceforge.netd152cab1c2b5d53d7d6e431570a77a4b4ab11da7<div class="markdown_content"><p>Do you have a git repo clone somewhere else than on sourceforge? It is inaccessible ATM.</p>
<p>b.</p>
<p>PS: I scratched my head for about an hour when I first saw your name in AWStats documentation/history and it sounded familiar. On an unrelated subject I must confess that hacking Dolibarr's invoice templates is a journey for french-almost-illiterate. :)</p></div>LogFormat: make colon in time zone specification optional2015-07-13T23:45:56Z2015-07-13T23:45:56ZBoštjan Škufcahttp://sourceforge.net/u/bostjanskufca/http://sourceforge.netf016be815f82c019ca8a46f29d02924923c1a14b<div class="markdown_content"><p>Hi Laurent,</p>
<p>let me state briefly my use case and problem:<br />
- I like date/time to be specified absolutely, so there is no doubt that it means<br />
- thus the only applicable format is full ISO 8601 format, which contains no literal names, weird order of month/day, and exact TZ offset.</p>
<p>Apache does not support full ISO 8601 date+time+tz format. The next best option is to use %{}t directive to mimic it, like this:</p>
<p>LogFormat "%{%Y-%m-%dT%H:%M:%S%z}t ..." format-name</p>
<p>Unfortunately this does not mimic it completely, as strftime's %z does not include colon character separator between hour and minute in TZ offset specification.</p>
<p>Sample full ISO 8601 time: 2015-07-10T22:38:39+00:00<br />
Best Apache approximation: 2015-07-10T22:38:39+0000 (note the missing colon)</p>
<p>AWStats supports full ISO8601 time specification (compliments!). But it would be splendid, if the colon character in time5 would be made optional, so that either +/-xx:xx and +/-0000 would match.</p>
<p>What do you think?</p>
<p>The patch is available here:<br />
<a href="http://source.a2o.si/patches/awstats-7.3-logformat-timezone-colon-optional.diff" rel="nofollow">http://source.a2o.si/patches/awstats-7.3-logformat-timezone-colon-optional.diff</a></p>
<p>I can provide a git pull request for this, if requested.</p>
<p>b.</p></div>LogFormat: match literal content2015-07-13T23:36:00Z2015-07-13T23:36:00ZBoštjan Škufcahttp://sourceforge.net/u/bostjanskufca/http://sourceforge.net932bedfb33e8df422b81cfa143c27e56425bd39f<div class="markdown_content"><p>Hi Laurent,</p>
<p>I've created a patch that allows literal strings in LogFormat. It is available here:<br />
<a href="http://source.a2o.si/patches/awstats-7.3-logformat-match-literal.diff" rel="nofollow">http://source.a2o.si/patches/awstats-7.3-logformat-match-literal.diff</a></p>
<p>Reason:<br />
I have quite extended log format and I have data prefixed with short field names which make manual looking at log file more pleasant - more readable.</p>
<p>The problem with AWStats is that ATM it has no way to match custom strings that are attached to content fields in LogFormat. This patch adds this ability.</p>
<p>My LogFormat in apache:<br />
LogFormat "%{%Y-%m-%dT%H:%M:%S%z}t r=%a l=%A tls=0 proto=%H vh=%V vhc=%v time=%D st=%&gt;s bytes=%O keep=%k conn=%X \"%r\" \"%{Referer}i\" \"%{User-Agent}i\"" custom-default-notls</p>
<p>Sample log entry produced:<br />
2015-07-13T23:26:27+0000 r=2a01:260:1010:1010::130 l=2a01:260:1010:1010::144 tls=1 proto=HTTP/1.1 vh=vhost.teon.si vhc=vhost.teon.si time=6783 st=302 bytes=5993 keep=0 conn=- "GET / HTTP/1.1" "-" "check_http/v2.0.3 (nagios-plugins 2.0.3)"</p>
<p>Caveat:<br />
This patch is simple and only allows matching literal content, if it is located as prefix to field value. For example:<br />
- "bytes=%bytesd" works if entry in logfile is "bytes=1234".<br />
- "size=%bytesdB" would not work, as %bytesd is not explicitly defined in awstats. It is only defined as regex %bytesd$, which is not easy to convert for my purpose, even if log entry would be is syntactically correct in this case "size=1234B" (according to LogFormat apache directive).</p>
<p>I can provide a git pull request for this, if requested.</p>
<p>What do you think?</p>
<p>b.</p></div>#97 Plugin: Export To CSV2014-10-31T21:57:37Z2014-10-31T21:57:37ZEdJhttp://sourceforge.net/u/ait109/http://sourceforge.neted2fc93afda3d85a5b51704c4a95732bae66cf77<div class="markdown_content"><p>I had this error as well. I ended up creating a new .pm file and copying one section of code at time to try and determine what was the problem. By the end I had copied the ENTIRE code over and guess what - it ran. Well, by ran I mean it didn't give me that error but there were other problems that needed to be fixed before it was usable. PM me for details. </p></div>#97 Plugin: Export To CSV2014-10-21T09:24:39Z2014-10-21T09:24:39Zchronoelhttp://sourceforge.net/u/chronoel/http://sourceforge.netf885e91eb68acefa8f30bcaeb407a5f0ff3a580f<div class="markdown_content"><p>I get this error when trying to load the export_to_csv plugin</p>
<p>Error Message shown below: "export_to_csv.pm did not return a true value at awstats.pl line 3186."</p>
<p>What could be the problem?</p></div>#196 Average Time Taken for Awstats 7.02014-10-16T12:49:15Z2014-10-16T12:49:15ZQuasarhttp://sourceforge.net/u/quasaro/http://sourceforge.net1a9f3dceb120e81a79a157411bc66e854009eece<div class="markdown_content"><p>Hi!</p>
<p>Thanks a lot for your work. It works ok, but I think the response time are in "ms", while the report is writing "s". Can you please confirm?</p>
<p>Thanks</p></div>#212 CVE-2006-22372014-09-21T23:02:06Z2014-09-21T23:02:06ZLaurent Destailleur (Eldy)http://sourceforge.net/u/eldy/http://sourceforge.net122c8819caa083760728d28483e551cc107721c4<div class="markdown_content"><ul>
<li><strong>status</strong>: accepted --&gt; closed</li>
</ul></div>#212 CVE-2006-22372014-09-21T23:01:50Z2014-09-21T23:01:50ZLaurent Destailleur (Eldy)http://sourceforge.net/u/eldy/http://sourceforge.net706e90f546d8cd086c0981868f8cf447165c2388<div class="markdown_content"><ul>
<li><strong>status</strong>: open --&gt; accepted</li>
<li><strong>Group</strong>: --&gt; </li>
</ul></div>