System Administration IBM HTTP Server documentation
Pertains to AIX users
Pertains to Windows users

Logging Fast Response Cache Accelerator requests

Note: The Fast Response Cache Accelerator (FRCA), also known as the Cache Accelerator, is supported on AIX and Windows operating systems.

This section provides information on logging FRCA requests. A general overview discusses the Cache Accelerator access log path and name. Links to related topics appear at the end of this section.

 

Understanding the Cache Accelerator access log

The 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. Use the normal Apache logging directives to log requests that are not served by the Cache Accelerator to separate log files.

This log provides a useful way to verify that caching is enabled and to identify cached files.

Even though you can cache a particular file, it might not always be served from the cache.

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 action enables the log file to process without having to stop and restart the server. Under heavy load conditions the log file can grow rapidly. Provide sufficient space on the hard drive for storage.

For each request served out of the Cache Accelerator, a log entry in the access log shows the:

  • Source host address
  • Date and time of the request
  • HTTP method of the request and what was requested
  • HTTP return code, which indicates whether the request was honored
  • Size of the returned data

 

A log entry can also optionally show the:

  • Target virtual host (use formatting option V-CLF or V-ECLF)
  • Referer (use formatting option ECLF or V-ECLF)
  • User agent (use formatting option ECLF or V-ECLF)

 

 

Finding related information

     (Back to the top)