From: eldy <> Date: Sat, 5 Apr 2003 16:20:48 +0000 (+0000) Subject: Updated documentation. X-Git-Tag: AWSTATS_5_5_BETA~40 X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=3f8cf9b3cf0f84eba6be79e02740ba1db52eb0ab;p=thirdparty%2FAWStats.git Updated documentation. --- diff --git a/docs/awstats_glossary.html b/docs/awstats_glossary.html index 0e483dc4..9dc1f202 100644 --- a/docs/awstats_glossary.html +++ b/docs/awstats_glossary.html @@ -41,7 +41,8 @@ The period shown by AWStats reports is by default the current month.
However if you use AWStats as a CGI you can click on the "year" link to have a report for all the year. In a such report, period is full year, so Unique Visitors are number of hosts that have made at least 1 hit on 1 page of your web site during those year.
-
+ +
Visits:
Number of visits made by all visitors.
@@ -49,37 +50,44 @@ Think "session" here, say a unique IP accesses a page, and then requests three o between any of the requests, all of the "pages" are included in the visit, therefore you should expect multiple pages per visit and multiple visits per unique visitor (assuming that some of the unique IPs are logged with more than an hour between requests)
-
+ +
Pages:
The number of "pages" logged. Only files that don't match an entry in the NotPageList config parameter (and match an entry of OnlyFiles config parameter if used) are counted as "Pages". Usually pages are reserved for HTML files or CGI files, not images nor other files requested as a result of loading a "Page" (like js,css... files).
-
+ +
Hits:
Any files requested from the server (including files that are "Pages") except those that match the SkipFiles config parameter.
-
+ +
+ Bandwidth:
Total number of bytes downloaded.
-
+ +
Entry Page:
First page viewed by a visitor during its visit.
Note: When a visit started at end of month to end at beginning of next month, you might have an Entry page for the month report and no Exit pages.
That's why Entry pages can be different than Exit pages.
-
+ +
Exit Page:
Last page viewed by a visitor during its visit.
Note: When a visit started at end of month to end at beginning of next month, you might have an Entry page for the month report and no Exit pages.
That's why Entry pages can be different than Exit pages.
-
+ +
Session Duration:
The time a visitor spent on your site for each visit.
@@ -87,13 +95,376 @@ Some Visits durations are 'unknown' because they can't always be calculated. Thi - Visit was not finished when 'update' occured.
- Visit started the last hour (after 23:00) of the last day of a month (A technical reason prevents AWStats from calculating duration of such sessions).
-
+ +
Grabber:
A browser that is used primarily for copying locally an entire site. These include for example "teleport", "webcapture", "webcopier"...
-
+
+ +HTTP Status Codes:
+ +HTTP +status codes are returned by web servers to indicate the status of a request. +The status code is a 3-digit code indicating the particular response. The +first digit of this code identifies the class of the status code. The remaining +2 digits correspond to the specific condition within the response class. +The following table outlines all status codes defined for the HTTP/1.1 +draft specification outlined in IETF +rfc 2068.  +They are classified in 5 categories:
+ + + + + + + +
+ +1xx class - Informational +
Informational status codes are provisional +responses from the web server... they give the client a heads-up on what +the server is doing. Informational codes do not indicate an error condition.  +
  + + + + + + + + + + + + +
100100 +Continue +
The continue status code tells the +browser to continue sending a request to the server. 
101101 +Switching Protocols +
The server sends this response when +the client asks to switch from HTTP/1.0 to HTTP/1.1 
+ +

2xx class - Successful +
This class of status code indicates +that the client's request was received, understood, and successful.  +
  + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
200200 +Successful
201201 +Created
202202 +Accepted
203203 +Non-Authorative Information
204204 +No Content
205205 +Reset Content
206206 +Partial Content +
The partial content success code is +issued when the server fulfills a partial GET request. This happens when +the client is downloading a multi-part document or part of a larger file. 
+ +

3xx class - Redirection +
This code tells the client that the +browser should be redirected to another URL in order to complete the request. +This is not an error condition.  +
  + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
300300 +Multiple Choices
301301 +Moved Permanently
302302 +Moved Temporarily
303303 +See Other
304304 +Not Modified
305305 +Use Proxy
+ +

4xx class - Client Error +
This status code indicates that the +client has sent bad data or a malformed request to the server. Client errors +are generally issued by the webserver when a client tries to gain access +to a protected area using a bad username and password.  +
  + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
400400 +Bad Request
401401 +Unauthorized
402402 +Payment Required
403403 +Forbidden
404404 +Not Found
405400 +Method Not Allowed
406400 +Not Acceptable
407400 +Proxy Authentication Required
408400 +Request Timeout
409409 +Conflict
410410 +Gone
411411 +Length Required
412412 +Precondition Failed
413413 +Request Entity Too Long
414414 +Request-URI Too Long
415415 +Unsupported Media Type
+ +

5xx class - Server Error +
This status code indicates that the +client's request couldn't be succesfully processed due to some internal +error in the web server. These error codes may indicate something is seriously +wrong with the web server.  +
  + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
500500 +Internal Server Error +
An internal server error has caused +the server to abort your request. This is an error condition that may also +indicate a misconfiguration with the web server. However, the most common +reason for 500 server errors is when you try to execute a script that has +syntax errors. 
501501 +Not Implemented +
This code is generated by a webserver +when the client requests a service that is not implemented on the server. +Typically, not implemented codes are returned when a client attempts to +POST data to a non-CGI (ie, the form action tag refers to a non-executable +file). 
502502 +Bad Gateway +
The server, when acting as a proxy, +issues this response when it receives a bad response from an upstream or +support server. 
503503 +Service Unavailable +
The web server is too busy processing +current requests to listen to a new client. This error represents a serious +problem with the webserver (normally solved with a reboot). 
504504 +Gateway Timeout +
Gateway timeouts are normally issued +by proxy servers when an upstream or support server doesn't respond to +a request in a timely fashion. 
505505 +HTTP Version Not Supported +
The server issues this status code +when a client tries to talk using an HTTP protocol that the server doesn't +support or is configured to ignore.
+