You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cxf.apache.org by "Tomás García (JIRA)" <ji...@apache.org> on 2019/06/28 07:48:00 UTC

[jira] [Created] (CXF-8062) MessageContext.HTTP_RESPONSE_CODE cannot be obtained if response code is not 200

Tomás García created CXF-8062:
---------------------------------

             Summary: MessageContext.HTTP_RESPONSE_CODE cannot be obtained if response code is not 200
                 Key: CXF-8062
                 URL: https://issues.apache.org/jira/browse/CXF-8062
             Project: CXF
          Issue Type: Bug
    Affects Versions: 3.3.2
            Reporter: Tomás García
         Attachments: 200.png, 401.PNG, cxf_dependencies.PNG

After a web service request, we do this:
{code:java}
responseCode = (Integer) ((BindingProvider) webServicePort).getResponseContext().get(MessageContext.HTTP_RESPONSE_CODE);
{code}
, to extract the Http response code, but we noticed that this only works in our case with 200 response codes from the server.

From what I could gather, it seems that the response context is not populated in cases where a 200 is not given. Example:

!401.PNG!

 As you can see only two instances of SCOPES are in the response context. When we receive a 200 from the web service, the response context contains this:

 !200.png! 

, which although you can't see it in the screenshot, it contains the HTTP_RESPONSE_CODE value, which it's the only thing we need, because we need to do some additional steps depending on that response code afterwards.

Right now, we're using a finicky way to obtain such http response code... the exception is a WebServiceException which contains a HTTPException which has the response code given by the server. We'd like to have a more reliable way since those exception signatures could just change over time if we update libraries / java versions we guess.

Here's the CXF dependencies in our project:
 !cxf_dependencies.PNG! 

Let us know if you need to know about anything else. 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)