Siebel inbound web service request fails with http-400 error when http header contains "Transfer-Encoding: chunked" when using Oracle HTTP Server for Siebel SWSE
Last updated on JULY 11, 2017
Applies to:Siebel CRM - Version 126.96.36.199  and later
Information in this document applies to any platform.
*** Checked for currency on 08-OCT-2014 ***
Siebel 188.8.131.52 SIA 
Customer uses Siebel web server extension on Oracle HTTP webserver. When they send an inbound web service into Siebel EAI OM, the web service request goes to the Oracle HTTP web server and fails with http 400 error. Upon investigation, it was discovered that the request header includes the "Transfer-Encoding:chinked" parameter and Oracle HTTP web server is not able to handle the "Transfer-Encoding:chinked" setting.
STEPS TO REPRODUCE:
The behaviour occurs as follows:
Use soapui to send an inbound web service into Siebel with web server on OHS.
In the soapui application, set HTTP Version = 1.1, set Chunking Threshold = 100 ( or some other value)
Send inbound request and got error the following error in the soap response:
Supplied input is not well formed or does not contain the expected data.(SBL-EAI-00137)
XML Hierarchy Converter error - empty input message, expecting an XML document in <Value> of input arguments(SBL-EAI-00246)
Check the "Transfer-Encoding: chunked" in the soap header within soapui, it would show that "Transfer-Encoding: chunked" is in the http header.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms