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.
Since it is possible to customize the access log, you can obtain more information about error conditions using that log file.
During testing, it is often useful to continuously monitor the error log for any problems.
Of course, storing the information in the access log is only the start of log management.
The next step is to analyze this information to produce useful statistics.
A typical configuration for the access log might look as follows.
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.
Various versions of Apache httpd have used other modules and directives to control access logging, including mod_log_referer, mod_log_agent, and the directive now subsumes the functionality of all the older directives.
The format of the access log is highly configurable.