[
https://issues.apache.org/jira/browse/AXIS2-5723?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17298315#comment-17298315
]
Robert Lazarski commented on AXIS2-5723:
----------------------------------------
1.6.1 is very old and unsupported.
If you can reproduce this issue with Axis2 1.7.9 then feel free to reopen this
issue.
> Handling of Http 202 in Axis 2 Rest. (HTTPSender)
> -------------------------------------------------
>
> Key: AXIS2-5723
> URL: https://issues.apache.org/jira/browse/AXIS2-5723
> Project: Axis2
> Issue Type: Bug
> Components: transports
> Affects Versions: 1.6.2
> Reporter: Ross Yakulis
> Priority: Blocker
>
> In HTTP Sender if a 202 is received, the code ignores any response body. The
> particular web service I am accessing I post a JSON body and the service
> returns a JSON response that contains an ID so that I can check back later
> for the result of my request. It seems to me that SC_OK and SC_ACCEPTED
> should be handled the same way.
> Note :
> http://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html
> 10.2.3 202 Accepted
> The request has been accepted for processing, but the processing has not been
> completed. The request might or might not eventually be acted upon, as it
> might be disallowed when processing actually takes place. There is no
> facility for re-sending a status code from an asynchronous operation such as
> this.
> The 202 response is intentionally non-committal. Its purpose is to allow a
> server to accept a request for some other process (perhaps a batch-oriented
> process that is only run once per day) without requiring that the user
> agent's connection to the server persist until the process is completed. The
> entity returned with this response SHOULD include an indication of the
> request's current status and either a pointer to a status monitor or some
> estimate of when the user can expect the request to be fulfilled.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
