api.elg outbound payload shows "Not written as the response is successful. See sk182786 for more information."

Product: Multi-Domain Security Management, Smart-1
Version: R81.10 (EOS), R81.20, R82
Last Modified: 2026-04-09

Symptoms

• api.elg shows the following:

`DATETIME INFO org.apache.cxf.interceptor.LoggingOutInterceptor.log:277 [THREAD-ID] - Outbound Message

ID: 507
Response-Code: 200
Content-Type: text/plain
Headers: {Content-Type=[text/plain], Date=[DATETIME]}
Payload: Not written as the response is successful. See sk182786 for more information.
--------------------------------------`

• Response-Code: 200 indicates a successful response, so no payload is logged.
  • Content-Type and Headers: Lists the message's content type (text/plain) and additional headers.
  • Payload: Notes that payload content is skipped for successful responses to conserve resources.

Cause

To optimize performance, the API does not log the outbound payload in api.elg when a call completes successfully with a 200 response code. However, if the response code differs from 200, the outbound payload automatically logs to api.elg for diagnostic purposes.

Enabling API debug mode overrides this default behavior, causing the outbound payload to log to api.elg for every API call, regardless of the response code.

Solution

We're here for you

Please log in / sign in to view solution

NOTE

This solution has been verified for the specific scenario, described by the combination of Product, Version and Symptoms. It may not work in other scenarios.