Logging
and Debugging for the IisProxy Module 
Logging
Log Levels
To specify the log level for the IisProxy module, specify the level in the log-level attribute for the < filter >, < extension >or < mapping > elements in the IisProxy.xml file. There are four log levels as shown in the table below.
Log Levels for the IisProxy Module
|
Log Level |
Description |
|
0 |
Error messages, filter and extension initialization |
|
1 |
Level 0 + warning messages, filter and extension configuration, processed requests |
|
2 |
Level 1 + info messages, filter operation |
|
3 |
Level 2 + data logging |
For production environments, we suggest using log level 1.
Additional Log Information
For debugging purposes, more log messages can be activated by severity or by area. Each severity and each area corresponds to a bit in the log-flags value. The log level is mapped to a set of bits in the log-flags variable and then OR-ed with the log-flags value.
See the tables below for the severity and logging area bit definitions.
Severity Bit Definitions
|
Bit Value |
Name |
Logged Information |
|
0x00000001 |
DEBUG |
Debug messages |
|
0x00000002 |
PASS_ON |
Messages for requests that have passed the filter unchanged |
|
0x00000004 |
FORWARD |
Messages for requests that have been modified by the filter for forwarding |
|
0x00000008 |
INFO |
Informational messages |
|
0x00000010 |
WARNING |
Warning messages |
|
0x00000020 |
ERROR |
Error messages |
|
0x00000040 |
|
<unused> |
|
0x00000080 |
|
<unused> |
Logging Area Definitions
|
Bit Value |
Name |
Logged Information |
|
0x00000100 |
INIT |
Common initialization messages |
|
0x00000200 |
CONFIG |
Configuration parsing messages |
|
0x00001000 |
FLT_INIT |
Filter initialization messages |
|
0x00002000 |
FLT_NOTIFY |
Messages for unknown notifications in the HttpFilterProc() function |
|
0x00004000 |
FLT_PASS |
Message for requests passed on for IIS processing |
|
0x00008000 |
FLT_WORK |
Message for requests marked for forwarding |
|
0x00010000 |
EXT_INIT |
Extension initialization messages |
|
0x00020000 |
EXT_WORK |
Messages for requests that enter the extension (before queuing) |
|
0x00040000 |
EXT_ERROR |
Extension error response messages |
|
0x00100000 |
PROXY_TIME_SHORT |
Short form messages for queuing and processing time (for offline performance analysis) |
|
0x00200000 |
PROXY_TIME |
Messages showing the lifetime of a Proxy object, for example, processing time |
|
0x00400000 |
PROXY_SSL |
Warnings from deriving information about a client SSL connection |
|
0x00800000 |
PROXY_RETRY |
Messages issued when the proxy object retries a target request |
|
0x01000000 |
PROXY_WORK |
Error messages from the proxy object |
|
0x04000000 |
POOL |
Connection pooling messages |
|
0x08000000 |
CONN_IIS |
IIS connection object lifecycle messages and I/O errors (from ReadClient() or WriteClient()) |
|
0x10000000 |
CONN_SAP |
SAP connection object lifecycle messages and I/O errors from the NI library or the SSL library |
|
0x20000000 |
MAPPING |
Mapping management messages |
|
0x80000000 |
DATA |
Data output to the data log file |
Debugging
Whilst logging can also be used for documentary purposes, debugging output is primarily meant for error analysis. The output data is not formatted as well and can only be viewed in a debugger or a debug monitor.
The 4 low-order bits are used to control the SAP developer trace for the SSL and NI libraries. These 4 bits are passed together with the <trace-path>value to the CTrcInit() call.
Debugging Bit Definitions
|
Bit Value |
Name |
Debug Information |
|
0x00000010 |
PREPROC_HEADERS |
Debug messages |
|
0x00000100 |
ERROR |
Internal error messages |
|
0x00000200 |
SAP |
SapInit() and SapExit() calls |
|
0x00000400 |
MEM |
Ctor and Dtor calls |
|
0x00000800 |
COMPRESS |
Compression decision and statistics |
|
0x00001000 |
CERT |
SSL info processing, certificate details |
|
0x00002000 |
WORKER |
Request processing details |
|
0x00004000 |
|
<unused> |
|
0x00008000 |
DOLOG |
Also write all log messages to the Debug output file |