[jira] Commented: (AXIS-1845) SOAP response returned in 202 error code

["Davanum Srinivas (JIRA)" <ax...@ws.apache.org>]

     [ http://issues.apache.org/jira/browse/AXIS-1845?page=comments#action_60904 ]
     
Davanum Srinivas commented on AXIS-1845:
----------------------------------------

As per BP 1.1 - http://www.ws-i.org/Profiles/BasicProfile-1.1-2004-08-24.html

R1112   An INSTANCE SHOULD use either a "200 OK" or "202 Accepted" HTTP status code for a response message that does not contain a SOAP envelope but indicates the successful outcome of a HTTP request.



> SOAP response returned in 202 error code
> ----------------------------------------
>
>          Key: AXIS-1845
>          URL: http://issues.apache.org/jira/browse/AXIS-1845
>      Project: Axis
>         Type: Bug
>  Environment: Axis 1.2RC3
>     Reporter: Amanda Hopgood
>     Assignee: Davanum Srinivas
>     Priority: Minor

>
> I have a system using Axis 1.2 RC3 which is communicating with a remote application. The remote application sends back 202 for success with a SOAPResponse in. Our application is expected to be able to decode the soapresponse returned.
> However we are using the standard HTTPSender, and this has code that means that the SOAPResponse is not decoded by Axis if its in a 202.
> This appears to be controlled by the readFromSocket method in the HTTPSender where it states:
>  	if ((returnCode > 199) && (returnCode < 300)) {
>         	if (returnCode == 202)
>             	return inp;
>             // SOAP return is OK - so fall through
> However the equivalent code doesn't appear to be in the CommonsHTTPSender (but we have other problems using Commons).
> Is it possible to update the current HTTPSender to remove the special case of 202, or make it configurable as to whether it treats 202 as a special case, or provide an extra sender that is same as HTTPSender but doesn't treat 202 differently to 200.

-- 
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
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira