Uploaded image for project: 'CXF'
  1. CXF
  2. CXF-3788

Allow CXF HTTP Client to handle HTTP 202 for twoway calls when the real response is sent back to the decoupled endpoint.

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 2.3.6, 2.4.2
    • Fix Version/s: 2.3.7, 2.4.3, 2.5
    • Component/s: Transports
    • Labels:
      None
    • Estimated Complexity:
      Moderate

      Description

      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.

        Attachments

          Activity

            People

            • Assignee:
              ay Akitoshi Yoshida
              Reporter:
              ay Akitoshi Yoshida
            • Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: