Note: The Fast Response Cache Accelerator is also known as the Cache Accelerator.
IBM HTTP Server can optionally create a log file that records requests served by the Cache Accelerator.
Enable the Cache Accelerator access log if you want to maintain a record of requests served by the Cache Accelerator. Requests that are not served by the Cache Accelerator can be logged using the normal Apache logging directives in separate log files.
You may want to use this log if you have enabled the Cache Accelerator for improved performance, and want to record information about requests served from the Cache Accelerator. It is also a useful way to verify that caching is enabled and way of determining which files are being cached.
Note that even though a file is cached, it may not necessarily be served from the cache every time. It depends on the sequence of events on a given connection.
The log file has a date stamp automatically appended to its name. Every day at midnight the server closes the current access log and creates a new one. This allows the log file to be processed without having to stop and restart the server. Note that under heavy load conditions the log file can grow rapidly and sufficient space must be available on the hard drive to store it.
For each request served out of the Cache Accelerator, an entry is made in the access log showing:
Optionally:
You can specify the path and file name of the Cache Accelerator access log file from the Administration Server.
AfpaLogFile file_path_and_name log_format