[
https://issues.apache.org/jira/browse/AXIS2-6061?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17941929#comment-17941929
]
Robert Lazarski commented on AXIS2-6061:
----------------------------------------
[~jwthomas] what content-type would you typically send and what format would
you expect 400 range errors to be in?
Do you think the accept header arriving at an Axis2 server that would define
the response, is a reliable mechanism?
Something like "Accept: text/html,application/xhtml+xml,application/xml;" is
typically used to define the response but that seems to me as permitting either
SOAP or html.
> Axis2 client parses soap envolope in case of a http-404
> -------------------------------------------------------
>
> Key: AXIS2-6061
> URL: https://issues.apache.org/jira/browse/AXIS2-6061
> Project: Axis2
> Issue Type: Bug
> Components: transports
> Affects Versions: 1.8.2
> Reporter: Manfred Weiss
> Assignee: Robert Lazarski
> Priority: Major
> Labels: pull-request-available
> Fix For: 2.0.1
>
>
> If the server returns a 404 with HTML, the client tries to parse a soap
> envelope and fails with:
> {code:java}
> com.ctc.wstx.exc.WstxUnexpectedCharException: Unexpected character 'd' (code
> 100) after '<!' (malformed comment?){code}
> I believe the problem was introduced with this commit:
> [https://github.com/apache/axis-axis2-java-core/commit/93d54beb5186803ea7dcb4a806c88d9ae2ea774f]
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org
For additional commands, e-mail: java-dev-h...@axis.apache.org
