[
https://issues.apache.org/jira/browse/CXF-3221?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12985551#action_12985551
]
Christian Schneider commented on CXF-3221:
------------------------------------------
Hi Chris. Redirects should be handled in HTTPConduit so they should not get to
the StaxInterceptor. We also have tests for redirects so the normal case should
work. Could you give me some more details under what circumstances the
exception appears? Ideal would be a small maven project that I can run and see
the problem. Could you also try with the just released 2.3.2 version maybe we
already fixed that.
> 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.
