Using Web Server Logging
Web Server logging is controlled by the base registry settings discussed in this section. For more information about these values, see Base Registry Settings.
With logging enabled, the Web Server appends relevant data to the current-httpd.log file at the end of each request. The current-httpd.log file is located in the directory that was specified by the LogFileDirectory value, included in the base registry settings. Each log entry contains the date and time of the request, the IP address of the client, the method that was used, the URL that was requested, the response code that was sent back, and, optionally, data that was appended by ISAPI extensions, ISAPI filters, or the ASP page.
When the size of the current-httpd.log file approaches the size that is specified in the MaxLogSize registry value, the logging process renames it to previous-httpd.log and creates a new file that is named current-httpd.log. By default, the MaxLogSize is 32K, measured in bytes. If a file that is named previous-httpd.log existed before this rollover occurs, that file is overwritten.
Note that if you set the logging to an invalid directory, but do not set the MaxLogSize registry value to zero (0), it can take 15 additional seconds for the Web Server to begin accepting connections. If the Web Server cannot create the log file, it does not abandon logging immediately, but attempts to reopen the log file once every second for 15 seconds. This functionality has been added because it is possible that the log file is being set up on a flash device that was not initialized by the time that the Web Server starts during the startup sequence. Therefore, if you do not want to perform logging, it is recommended that you set the MaxLogSize registry value to zero (0) to avoid this delay.