HTTP Request Logging

EFT Server can be instructed to log specific or all HTTP request headers. For this registry key to work, you must create a file called logging.cfg, save it in the EFT Server installation folder (e.g., (C:\Documents and Settings\All Users\Application Data\GlobalSCAPE\EFT Server Enterprise\logging.cfg), and configure it to log at the DEBUG level. Once this file is in place, EFT Server logs requests that require authentication and those that cause session-checking failures. When the registry key is set, then all HTTP request headers will be logged. The information is logged to a file named EFT.log in the EFT Server installation folder (e.g., (C:\Documents and Settings\All Users\Application Data\GlobalSCAPE\EFT Server Enterprise\).

     [HKEY_LOCAL_MACHINE\SOFTWARE\GlobalSCAPE Inc.\EFT Server 4.0\EFTClient]

EFT.log organizes logging levels as a hierarchy: TRACE, DEBUG, INFO, WARN, ERROR, FATAL, OFF. When you specify a logging level, each of the lower levels is also included. That is, if you specify DEBUG level, you also get INFO, WARN, ERROR, and FATAL logs. However, if you specify INFO, you will not log DEBUG or TRACE level activities.

     "log_request"=dword:1

   1 = enable "all request header" logging

   0 = disable "all request header" logging [default]

Appenders determine where the output of the logging goes. Each logger can have more than one appender and inherits appenders from parents by default. Appenders have an associated layout that determines the content of the log lines. EFT Server uses a RollingFileAppender with the TTCCLayout. With this layout, the log contains the name of the logger, date/time, thread id, the log line itself, and other things.

Below are examples from a logging.cfg file:

The file logging.cfg provides details of how EFT Server uses Log4Cplus. For more information about Log4cplus, refer to http://log4cplus.sourceforge.net/docs/html/classlog4cplus_1_1PropertyConfigurator.html#21e8e6b1440cc7a8a47b8fd14c54b239