Using ESB a SOAP Fault Generates Incorrect Code HTTP 200 Instead of HTTP 500
(Doc ID 973555.1)
Last updated on MARCH 07, 2019
Applies to:
Oracle SOA Suite - Version 11.1.1.1.0 and laterInformation in this document applies to any platform.
***Checked for relevance on 25-Oct-2011***
Symptoms
The SOAP/HTTP Web services standard specifies that when a SOAP Fault is generated, the corresponding HTTP Code with the SOAP Fault should be HTTP 500.
This is clearly mentioned in <Note 453951.1> How To Stop Client Application Receive HTTP 500 Error When BPEL Process Throws SOAP Faults as well.
However, when an ESB Service is invoked using SOAP and a fault occurs, it returns a HTTP 200 error code:
HTTP/1.x 200 OK
Date: Wed, 27 May 2009 23:04:39 GMT
Server: Oracle-Application-Server-10g/10.1.3.4.0 Oracle-HTTP-Server
Keep-Alive: timeout=15, max=100
Connection: Keep-Alive
Transfer-Encoding: chunked
Content-Type: text/html; charset=UTF-8
Date: Wed, 27 May 2009 23:04:39 GMT
Server: Oracle-Application-Server-10g/10.1.3.4.0 Oracle-HTTP-Server
Keep-Alive: timeout=15, max=100
Connection: Keep-Alive
Transfer-Encoding: chunked
Content-Type: text/html; charset=UTF-8
Cause
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
| Symptoms |
| Cause |
| Solution |
| References |