To set the access log preferences for the Administration Server

Steps

1. Access the Administration Server and click the Preferences tab.

2. Click the Set Access Log Preferences link. The Set Access Log Preferences page displays.

3. Select the resource from the drop-down list or click the Regular Expression button, enter a regular expression, and click OK.

4. Specify whether or not to log client accesses. This requires Domain Name Service (DNS) to be enabled.

5. Specify the absolute path for the access log file. As a default, the log files are kept in the logs directory in the server root. If you specify a partial path, the server assumes the path is relative to the logs directory in the server root.

   If you are editing the entire server, the default value for this field is $accesslog, the variable that denotes the access log file for the server in the configuration file.

6. Choose whether or not to record domain names or IP addresses of the systems accessing the server in the access log.

7. Choose the type of log file format to use in the access log. The following options are available:

   • Use Common LogFile Format. Includes client’s host name, authenticated user name, date and time of request, HTTP header, status code returned to the client, and content length of the document sent to the client.

     • Only Log. Allows you to choose which information will be logged. You can choose from the following flexible log format items:

       • Client Hostname. The hostname (or IP address if DNS is disabled) of the client requesting access.

       • Authenticate User Name. If authentication was necessary, you can have the authenticated user name listed in the access log.

       • System Date. The date and time of the client request.

       • Full Request. The exact request the client made.

       • Status. The status code the server returned to the client.

       • Content Length. The content length, in bytes, of the document sent to the client.

       • HTTP Header, “referer”. The referer specifies the page from which the client accessed the current page. For example, if a user was looking at the results from a text search query, the referer would be the page from which the user accessed the text search engine. Referers allow the server to create a list of backtracked links.

       • HTTP Header, “user-agent”. The user-agent information--which includes the type of browser the client is using, its version, and the operating system on which it is running--comes from the User-agent field in the HTTP header information the client sends to the server.

       • Method. The HTTP request method used such as GET, PUT, or POST.

       • URI. Universal Resource Identifier. The location of a resource on the server. For example, for http://www.a.com:8080/special/docs, the URI is special/docs.

       • Query String Of The URI. Anything after the question mark in a URI. For example, for http://www.a.com:8080/special/docs?find_this, the query string of the URI is find_this.

       • Protocol. The transport protocol and version used.

       If you choose a custom format, type it in the Custom Format field.

8. Click OK.

9. Click Restart Required. The Apply Changes page displays.

10. Click the Restart Proxy Server button to apply the changes.