From: eldy <>
Date: Wed, 11 Sep 2002 22:50:41 +0000 (+0000)
Subject: Updated documentation.
X-Git-Tag: AWSTATS_5_0_BETA~55
X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=419d06868974a4cfda3e89bf2709080b316b5dd2;p=thirdparty%2FAWStats.git

Updated documentation.
---

diff --git a/docs/awstats_faq.html b/docs/awstats_faq.html
index d79418d9..ba0c8bd7 100644
--- a/docs/awstats_faq.html
+++ b/docs/awstats_faq.html
@@ -118,15 +118,16 @@ and proxy server log files. Some FTP servers are also supported.<br>
 The only requirement is "Your log file must contain required information".<br>
 This is example of possible log format:<br>
 <i>
-Apache combined log format (known as NCSA combined log format or XLF or ELF format) (See FAQ for this 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>
 ProFTP server<br>
-...<br>
+A lot of web/wap/proxy 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.
-But a lot of users asked me for it, so AWStats support it. However, a lot of interesting advanced features can't work: browsers, os's, keywords, robot detection...).
+But a lot of users asked me for it, so AWStats support it.
+However, a lot of interesting advanced features can't work: browsers, os's, keywords, robot detection...).
 </i><br>
 See also <a href="#PERSONALIZEDLOG">F.A.Q.: LOG FORMAT SETUP OR ERRORS </a>.<br>
 <br>
diff --git a/docs/awstats_security.html b/docs/awstats_security.html
index ac139204..073743db 100644
--- a/docs/awstats_security.html
+++ b/docs/awstats_security.html
@@ -119,6 +119,7 @@ require valid-user<br>
 </i><br>
 Then edit each config/domain file you want to be protected to set <a href="awstats_config.html#AllowAccessFromWebToAuthenticatedUsersOnly">AllowAccessFromWebToAuthenticatedUsersOnly</a> to 1.<br>
 You can also edit list of authorized users in the <a href="awstats_config.html#AllowAccessFromWebToFollowingAuthenticatedUsers">AllowAccessFromWebToFollowingAuthenticatedUsers</a> parameter.<br>
+You can also specify a range of allowed browsers IP Addresses with the <a href="awstats_config.html#AllowAccessFromWebToFollowingIPAddresses">AllowAccessFromWebToFollowingIPAddresses</a> parameter.<br>
 <br>
 Other tip: If you define <b>AWSTATS_CONFIG</b> environment variable in your web server environment (Adding
 <i>SetEnv AWSTATS_CONFIG myconfigvalueformydomain</i> with other directives in your Apache VirtualHost config), AWStats
@@ -137,7 +138,7 @@ Setup is very easy (No need of particular setup). Statistics are dynamic.<br>
 No way to prevent stats for config/domain to be seen by a user that known the
 config/domain name and the url syntax to see stats of a particular config/domain.<br>
 <font color=blue><b>How</b></font>:<br>
-No particular things to do.<br>
+No particular things to do (You can however use <a href="awstats_config.html#AllowAccessFromWebToFollowingIPAddresses">AllowAccessFromWebToFollowingIPAddresses</a> parameter).<br>
 <br>
 <br>
 <br>