cxf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Daniel Kulp (JIRA)" <j...@apache.org>
Subject [jira] Assigned: (CXF-3221) StaxInInterceptor doesn't handle redirects well
Date Fri, 21 Jan 2011 22:31:45 GMT

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

Daniel Kulp reassigned CXF-3221:
--------------------------------

    Assignee: Christian Schneider


I'm going to assign this to Christian.  For 2.3.2, he did some work in the HTTPConduit to
get it to throw more reasonable exceptions in some of these types of cases.    If this isn't
covered by that, then it probably should be.   

Christian: can you take a look?

> StaxInInterceptor doesn't handle redirects well
> -----------------------------------------------
>
>                 Key: CXF-3221
>                 URL: https://issues.apache.org/jira/browse/CXF-3221
>             Project: CXF
>          Issue Type: Bug
>    Affects Versions: 2.2.7
>            Reporter: Chris Wilson
>            Assignee: Christian Schneider
>
> StaxInInterceptor detects the wrong content type of the response, and throws an exception,
in handleMessage().
> However it doesn't check the response code to see whether it's a redirect. In this case
there may not be any useful HTML output, so the INVALID_HTML_RESPONSETYPE exception will not
contain any information that helps to debug the fault.
> This could alternatively be seen as the job of HTTPConduit.WrappedOutputStream, which
checks for 404 errors (HTTP_NOT_FOUND), but assumes that there will always be a response body.
> It's also not clear what the accessed URL was, to help with debugging.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message