This section describes how PCA and pipeline hits are logged when they exceed the maximum permitted size.
Monitoring the pipeline
When a pipeline hit exceeds the configured maximum size, an Event Log entry is generated, and its message indicates the size of the offending hit.
Monitoring PCA
Response size: When the response portion of a hit exceeds the maximum permitted size, the response is truncated to the max size, and a log entry similar to the following is inserted:
TLAPI: Truncating body because RequestLength(%u) > MaximumRequestLength(%u)
for connection: %sRequest size: When the request portion of a hit exceeds the maximum permitted size, the hit is dropped, and a log entry similar to the following is inserted:
TLAPI: Dropping hit because RequestHeaderBytesRead(%u) >=
MaximumRequestLength(%u) for connection: %sThe default value for the Max Request Size setting is 1.5MB, or 1572864 bytes.
Whole hit size: When a request and its associated response (called a hit) exceeds the maximum permitted size, it is dropped.
Before the hit is sent from the PCA to its delivery target the size of the hit is checked. If the size exceeds the maximum data size allowed (2MB by default), the hit is dropped, and a log entry is similar to the following is inserted:
TLAPI: Data size (%u) exceeds default MaxDataSize (%u) for connection: %s