My Oracle Support Banner

dapIF Fails to Handle Non-CRLF Terminated Content-Length Based SOAP/HTTP Responses (Doc ID 1917961.1)

Last updated on JULY 22, 2022

Applies to:

Oracle Communications Network Charging and Control - Version 5.0.0 and later
Oracle Solaris on SPARC (64-bit)


In Network Charging and Control (NCC), Data Access Pack (DAP) is used to interface third party Application Service Providers (ASPs) over HTTP/SOAP for reasons such as retrieving subscriber information or to initiate remote processing to be performed.

If the response from the ASP is non-chunked (ie. Content-Length based) and not terminated with a Carriage Return/Line Feed (CR-LF) character, then dapIF assumes the response has not been completely received and fails the transaction when the ASP closes the connection.

No errors can be seen in the dapIF log, however if debug is enabled, this behaviour can be seen:

1. A response comes back from the ASP which is Content-Length based.  In this case, 1331 bytes/octets are expected in the HTTP/SOAP body


4. The DAP2 node in the Control Plan will then take the Error exit.


This difference can also be visualised in Wireshark in the packet bytes after the closing brace ">" (3E) character:

1. CR-LF Terminating Characters (0D 0A)

2. No CR-LF Terminating Characters


Changes to the ASP to return non-CR-LF terminated SOAP/HTTP responses.


To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!

In this Document

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.