Contact us

← What's new

An unreadable REST or XML response is logged and explained

When a REST or SOAP backend answered with something that was not the JSON or XML it promised, [[product:ol-integration|OL Integration]] reported a parse failure that said nothing about what actually arrived — commonly a proxy error page or a sign-in redirect.

One warning is now written with the HTTP status, the content type, the host and the start of the body, and the error raised in its place names the status and content type without repeating the body. Body logging is on by default and can be turned off per connector, or for every connector at once, where responses may carry sensitive data.

Read more