Web Service returns HTTP 400 Bad Request (Mix Of SOAP 1.1 And SOAP 1.2) On SOAP Fault Exceptions
Last updated on MARCH 02, 2017
Applies to:Siebel eCommunications Call Center - Version 18.104.22.168.9 [IP2013] and later
Information in this document applies to any platform.
Checked for relevance on 28-JUN-2016
When a SOAP Fault exception is raised from Siebel inbound web services sends it sends a response code 400.
Sebel is behaving somewhat mixed between SOAP 1.1 and SOAP 1.2.
In Soap 1.1 response code 500 is only valid for Soap Faults, and for Soap 1.2 response code 400 and 500 are valid.
Furthermore a Soap 1.1 response is required to send a content type of text/xml, while Soap 1.2 are required to send a content type application/soap+xml
On Sending a request, which is not known to siebel, it responds with a response code 400 (Soap 1.2), however the content-type is text/html (Soap 1.1).
Will it be possible to either do one of the following to enforce compliance to either Soap 1.1 or Soap 1.2:
1. Either the content-type is corrected i.e. set to application/soap+xml
2. Alternatively we would like to only get response code 500.
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