[jira] [Closed] (CXF-3788) Allow CXF HTTP Client to handle HTTP 202 for twoway calls when the real response is sent back to the decoupled endpoint.

["Aki Yoshida (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/CXF-3788?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Aki Yoshida closed CXF-3788.
----------------------------

    Estimated Complexity: Moderate  (was: Unknown)

> Allow CXF HTTP Client to handle HTTP 202 for twoway calls when the real response is sent back to the decoupled endpoint.
> ------------------------------------------------------------------------------------------------------------------------
>
>                 Key: CXF-3788
>                 URL: https://issues.apache.org/jira/browse/CXF-3788
>             Project: CXF
>          Issue Type: Bug
>          Components: Transports
>    Affects Versions: 2.3.6, 2.4.2
>            Reporter: Aki Yoshida
>            Assignee: Aki Yoshida
>             Fix For: 2.3.7, 2.4.3, 2.5
>
>
> CXF's HTTP Client can currently only handle HTTP 202 for oneway calls. This can lead to problems for twoway calls using a decouple endpoint when the server sends back the actual response to the decoupled endpoint and just an HTTP 202 response with no content to the HTTP response channel.
> This problem was not noticed until now in various CXF-to-CXF tests, as the CXF server returns an HTTP 200 with an empty SOAP envelope (not filled) to the HTTP response channel.
> But this behavior does not conform to the standard, it will be fixed with CXF-3768. CXF-366 and CXF-981 are also related to CXF-3768.
> This jira ticket is created so that this patch can be ported to the older releases. And this patch needs to precede the patch for CXF-3768.
>  

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira