From: eldy <>
Date: Thu, 17 Oct 2002 14:58:06 +0000 (+0000)
Subject: Change to allow AWStats to analyze Windows Media Server files.
X-Git-Tag: AWSTATS_5_1_BETA~14
X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=87efd8fd35cf148d92be522ef6bdd48a8ca2efa6;p=thirdparty%2FAWStats.git

Change to allow AWStats to analyze Windows Media Server files.
---

diff --git a/docs/awstats_changelog.txt b/docs/awstats_changelog.txt
index 64b8996c..b1b4fead 100644
--- a/docs/awstats_changelog.txt
+++ b/docs/awstats_changelog.txt
@@ -4,13 +4,21 @@ AWStats Changelog
 
 5.1
 
+- Better support for ftp log files.
+- Better support for mail log files.
+- Can analyze streaming log files (Windows Media Server).
+- Added choice of month and year in list boxes (when used as CGI).
+- The data values for month and days are reported in main page under the
+  graph, no need to change page.
 - New feature: ShowxxxStats parmaters accept codes to decide which columns to
   show in chart.
 - New parameter: Added SkipUserAgents parameter to exclude some user agent
   from statistics.
-- New parameter: Added URLCaseSensitive.
+- New parameter: Added URLNotCaseSensitive.
 - New parameter: Added URLWithQueryWithoutFollowingParameters to exclude some
   parameters from URL when URLWithQuery is on.
+- Fixed: Wrong window was opened when clicking on flag link when
+  UseFramesWhenCGI was on.
 - Fixed: Fixed pb in refreshing page when clicking on "Update Now" link (no
   need to force the refresh).
 - Fixed: Pb with SAMBAR server ('Expires' line appears at the top of pages).
@@ -25,6 +33,8 @@ AWStats Changelog
 - Can use the #include "configfile" directive in config files.
 - Added week-end color on week-end days in monthdayvalues report.
 - Added 'spider' and 'crawler' as generic robots.
+- Added awstats_updateall.pl tool.
+- Remove common2combined.pl tool (useless).
 - Updated graph colors.
 - Updated documentation.
 - Updated database.
diff --git a/docs/awstats_faq.html b/docs/awstats_faq.html
index 68d3ae0b..d0808a2e 100644
--- a/docs/awstats_faq.html
+++ b/docs/awstats_faq.html
@@ -100,19 +100,20 @@ FAQ-SEC200 <a href="#WORMS">How to manage log files (and statistics) corrupted b
 <b><u>FAQ-ABO100 : WHICH SERVER LOG FILES OR OS ARE SUPPORTED ?</u></b><br>
 AWStats can works with :<br>
 - All web server able to write log file with a <u>combined log format (XLF/ELF)</u> like Apache,
-a <u>common log format (CLF)</u> like Apache or Squid, an <u>W3C log format</u> like IIS 5.0 or higher (Some users have
-reported that you can setup your log format to W3C with IIS 4.0 but you need a service pack 6)<br>
-- Most of all others Web/Wap/Proxy servers.<br>
-- Some FTP, syslog and mail log files.<br>
+a <u>common log format (CLF)</u> like Apache or Squid, a <u>W3C log format</u> like IIS 5.0 or higher,
+or any other log format that contains all information AWStats expect to find.<br>
+- Most of all others Web/Wap/Proxy/Streaming servers.<br>
+- Some FTP, Syslog or Mail log files.<br>
 Because AWStats is in Perl, it can works on all Operating Systems.<br>
 Examples of used platforms (bold means 'tested by author', others were reported by AWStats users to work correctly) :<br>
 <table bgcolor=#F0F0F0 width="100%" class=CFAQ><tr class=CFAQ><td class=CFAQ>
 <u>OS:</u><br>
 <b>Windows 2000</b>, <b>Windows NT 4.0</b>, Windows Me, <b>Linux</b>, Macintosh, <b>Solaris</b>, <b>Aix</b>, BeOS, ...<br>
-<u>Web/Wap/Proxy/FTP/Mails servers</u><br>
-<b>Apache</b>, <b>IIS 5.0</b>, WebStar, WebLogic, WebSite, Tomcat, Squid, Sendmail, Roxen, Resin, ProFTP, Lotus Notes/Domino, IPlanet, IceCast, Zope, www4mail, ...<br>
+<u>Web/Wap/Proxy/FTP/Mails/Streaming servers</u><br>
+<b>Apache 1.3.x and 2</b>, <b>IIS 5.0</b>, WebStar, WebLogic, WebSite, <b>Windows Media Server</b>, Tomcat, <b>Squid</b>, <b>Sendmail</b>,
+Roxen, Resin, <b>ProFTP</b>, Lotus Notes/Domino, IPlanet, IceCast, Zope, www4mail, ...<br>
 <u>Perl interpreters:</u><br>
-<b>ActivePerl 5.6</b>, <b>Perl 5.8</b>, <b>Perl 5.6</b>, <b>Perl 5.0</b>, mod_perl for Apache, ...<br>
+<b>ActivePerl 5.6</b>, <b>Perl 5.8</b>, <b>Perl 5.6</b>, <b>Perl 5.0</b>, <b>mod_perl for Apache</b>, ...<br>
 </td></tr></table>
 <br>
 
@@ -127,8 +128,9 @@ This is example of possible log format:<br>
 Apache combined log format (known as NCSA combined log format or XLF or ELF format)<br>
 IIS 5.0+ log format (known as W3C format)<br>
 Webstar native log format<br>
+Windows Media Server<br>
 ProFTP server<br>
-A lot of web/wap/proxy servers log format<br>
+A lot of web/wap/proxy/streaming servers log format<br>
 Apache common log format (AWStats can now analyze such log files but such log files does not contain all information
 AWStats is looking for. The problem is in the content, not in the format). I think analyzing common log files is not
 interesting because there is a lot of missing information: no way to filter robots, find search engines, keywords, os, browser.