axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Eran Chinthaka (JIRA)" <j...@apache.org>
Subject [jira] Resolved: (AXIS2-136) HTTP 500 status not set when a SOAP fault is thrown and not accepted by the Client API
Date Fri, 12 Aug 2005 10:18:13 GMT
     [ http://issues.apache.org/jira/browse/AXIS2-136?page=all ]
     
Eran Chinthaka resolved AXIS2-136:
----------------------------------

    Resolution: Fixed

Seems like Deepal has fixed the original bug of not sending HTTP 500 and he has opened another
on this handling in client side.

> 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
>     Assignee: Deepal Jayasinghe
>      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