Invoke Oracle Integration When a Payload is Not Expected

If the Salesforce application invokes Oracle Integration with an Apex program and a payload is not expected, you must set the Content-Length header to 0 in the Apex program on the Salesforce side.

As per the HTTP/1.0 Draft RFC and also HTTP/1.1, which is backward compatible with HTTP/1.0 , application clients must send a valid Content-Length header if the entity body must be sent. The Content-Length header can be zero or more.

In Oracle Integration, you either need to pass the Content-Length header (0 is a valid value) or pass Transfer-Encoding. A Transfer-Encoding value of chunked is assumed.