KB Article #176852

Payload logging with a Connect to URL filter - incorrect content logged for backend server

Problem

The payload logging for a backend server using a "connect to URL" filter doesn't match the actual content found on the wire or received by the server.
Note the policy doesn't use the default "${content.body}" attribute in the "connect to URL" filter but instead uses another attribute with some processed content.

Payload logging always logs the content.body attribute.

Resolution

In the "connect to URL" filter always use the default "${content.body}" for the Request Body for correct payload logging.
This may need some modification to copy content attributes to the correct/default ${content.body} attribute in some policies.

This will be fixed to log the Body Request attribute in the next major release.

Still need help?

If this information wasn't helpful to you, just drop us a line. We'll get back to you as soon as possible.