Version: Boron-SR3.

Restconf call to Netconf-mounted router to fetch some data with Accept: json header results in severely truncated response payload.

The same call with Accept: xml header results in the entire payload correctly rendered.

Setting TRACE options for netconf within karaf shows the netconf data is indeed intact in the router's RPC response.

{set TRACE org.opendaylight.netconf.sal.connect.netconf, set TRACE org.opendaylight.netconf}

Attachments:
jsonoutputapi.txt:

• Example RestConf method used
• An example of the heavily-truncated JSON response
• The correct payload in the XML response to the same method.
• Snippet/example from karaf log showing Netconf RPC response payload
• (also in karaf log) A suspicious (or not) WARN about leading LF (0a) character (which can be seen in the NetconfXMLToMessageDecoder raw netconf response payload).