axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ruchith Udayanga Fernando (JIRA)" <j...@apache.org>
Subject [jira] Created: (AXIS2-136) HTTP 500 status not set when a SOAP fault is thrown and not accepted by the Client API
Date Wed, 10 Aug 2005 12:53:35 GMT
HTTP 500 status not set when a SOAP fault is thrown and not accepted by the Client API
--------------------------------------------------------------------------------------

         Key: AXIS2-136
         URL: http://issues.apache.org/jira/browse/AXIS2-136
     Project: Apache Axis 2.0 (Axis2)
        Type: Bug
  Components: transports  
    Versions: 0.91    
    Reporter: Ruchith Udayanga Fernando
     Fix For: 0.91


Seems like we are not setting HTTP 500 when Axis2 throws a SOAP Fault

Ref:
http://www.w3.org/TR/2003/REC-soap12-part0-20030624/#L26866

"If an error occurs processing the request, the HTTP binding specification requires that a
HTTP 500 "Internal Server Error" be used with an embedded SOAP message containing a SOAP fault
indicating the server-side processing error."

http://www.w3.org/TR/2003/REC-soap12-part0-20030624/#Example10


-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


Mime
View raw message