Updated documentation.

diff --git a/docs/awstats_faq.html b/docs/awstats_faq.html
index d486dda58ce388071c3780790ce1ceff2a3c7505..60252011438d323da2a6bd8e59305ee002db5361 100644 (file)
--- a/docs/awstats_faq.html
+++ b/docs/awstats_faq.html
@@ -639,9 +639,9 @@ I also use Webalizer, Analog (or another log analyzer) and it doesn't report the
 <font class=CSolution>SOLUTION:</font><br>
 If you compare AWStats results with an other log file analyzer, you will found some differences,
 sometimes very important. In fact, all analyzer (even AWStats) make "over reporting" because of the
-problem of proxy-servers and robots. However AWStats is one the most accurate and its "over reporting"
-is very low where all other analyzers, even the most famous, have a very high error rate (10% to 2x more than reality).<br>
-This is the most important reasons why you will find differences:<br>
+problem of proxy-servers and robots. However AWStats is one of the most accurate and its "over reporting"
+is very low where all other analyzers, even the most famous, have a VERY HIGH error rate (10% to 200% more than reality !).<br>
+<b>This is the most important reasons why you can find important differences:</b><br>
 <li> Some dynamic pages generated by CGI programs are not counted by some analyzer (ie Webalizer) like
 a "Page" (but only like a "Hit") if CGI prog does not end with a defined extension (.cgi, ...), so they are not included
 correctly in their statistics. AWStats use on oposite policy, assuming a file is a page except if 
@@ -663,6 +663,7 @@ but only "nearly" sorted because of cache and writing log engines used by server
 analyzers (commercial and not) assumes that log file is "exactly" sorted by hit date to calculate
 visits, entry and exit pages. AWstats has an advanced parsing algorithm that is able to count visits,
 entry and exit pages even if log file is only "nearly" sorted.<br>
+<b>There is also other reasons, however those points explains only small differences:</b><br>
 <li> To differenciate new visits of a same visitor, log analyers uses a visit time-out. If value differs,
 then results differ (on visit count and entry and exit pages).
 A such time-out is a fixed value (For example 60 minutes) meaning if a visitor make a hit
@@ -675,9 +676,12 @@ little differences, in visit count, between AWStats and another log analyzer eve
 their time-out are both defined to same value (because AWStats time-out is not exactly
 but nearly value defined).<br>
 <li> There is also differences in log analyzers databases and algorithms that make details of results less or more accurate:<br>
-AWStats has a larger browsers, os' and search engines database, so reports concerning this are more accurate.<br>
+AWStats has a larger browsers, os', search engines and robots database, so reports concerning this are more accurate.<br>
 AWStats has url syntax rules to find keywords or keyphrases used to find your site, but AWStats has also
 an algorithm to detect keywords of unknown search engines with unknown url syntax rule.<br>
+AWStats does not count twice (by default) redirects made by rewrite rules that makes two hits into
+log files but that are only one page "viewed".<br>
+Etc...<br>
 <br>
 
 <a name="DIFFERENCE_HOURS"></a><br>