[jira] Commented: (CXF-3221) StaxInInterceptor doesn't handle redirects well

["Chris Wilson (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/CXF-3221?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12995820#comment-12995820 ] 

Chris Wilson commented on CXF-3221:
-----------------------------------

Hi Christian,

The RITA RPC client (http://rita.logscluster.org/browser/rita/src/org/wfp/rita/rpc/RpcClientFactory.java), if configured to access the old server (http://rita.wfplogistics.org/rita/rpc/RpcServerInterface1), which sends redirects, should fail with this error.

Cheers, Chris.

> 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
>             Fix For: NeedMoreInfo
>
>
> 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.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira