When session data includes incomplete (truncated) XML Post data this will cause parsing errors during segment analysis.? The problem is verified by tracing RS Extractor log entries identifying bad tags to the hit data that has triggered the failure. Typically this is a POST request sometimes from the UI Capture library.? A valid UI Post includes these ending tags at the end of the XML1 section:

</ClientEventSet></Request>

The </Request> tag is added by the PCA when it wraps the XML data: &#133.? The UI data always ends in </ClientEventSet>.? If the XML data has truncated the point of truncation is visible before the </Request> tag.? If bad POST data is identified and dropped via Privacy rules session analysis can be restored.? Example criteria for finding and dropping incomplete UI hits:

HTTP_X_TEALEAF=ClientEvent (Optional but more precise)
REQUEST_METHOD=POST (Optional but more precise)
URL includes TeaLeafTarget
StatusCode=500
URL includes TeaLeafTarget

HTTP_X_TEALEAF=ClientEvent (Optional but more precise)
REQUEST_METHOD=POST (Optional but more precise)
URL includes TeaLeafTarget
StatusCode=200
ReqCancelled=Server (or ReqCancelled <> False)

It is recommended (especially for the Status 200 example) to create ReqSet rules to tag the suspicious hits.? Review the tagged hits to determine how often they occur and whether the criteria is finding only incomplete XML sections.? When you are satisfied that these hits should be dropped either replace the ReqSet rule with a DropHit rule or add a DropHit rule down stream to find? and drop the tagged hits.

00001436