On unix systems, you can accomplish this using: The server access log records all requests processed by the server.
The location and content of the access log are controlled by the Custom Log directive.
Any information written to by a CGI script will be copied directly to the error log.
It is not possible to customize the error log by adding or removing information.
In addition, log files may contain information supplied directly by the client, without escaping.
Therefore, it is possible for malicious clients to insert control-characters in the log files, so care must be taken in dealing with raw logs.
The second entry lists the severity of the error being reported.
The Log Level directive is used to control the types of errors that are sent to the error log by restricting the severity level.
During testing, it is often useful to continuously monitor the error log for any problems.The server reports the file-system path (as opposed to the web path) of the requested document.A very wide variety of different messages can appear in the error log. The error log will also contain debugging output from CGI scripts.This document describes how to configure its logging capabilities, and how to understand what the logs contain.give people write access to the directory the logs are stored in without being aware of the consequences; see the security tips document for details.
Search for erros dating:
Log analysis in general is beyond the scope of this document, and not really part of the job of the web server itself.