[
https://issues.apache.org/jira/browse/AXIS2-6061?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17941906#comment-17941906
]
Jeff Thomas commented on AXIS2-6061:
------------------------------------
I created a ticket for the same issue here AXIS2-6091.
I don't necessarily agree with this statement: "It simply makes no sense to
expect a SOAP envelope with an HTTP-404.".
If the endpoint is to query a resource say by ID and that resource is not
found, an endpoint may very well return a 404 with a SOAP fault. It depends on
the endpoint.
It is also possible that the 404 returns a HTML page (like Tomcat) if the
endpoint is not available.
I would hope one can distinguish the two responses by their content-types.
> 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
