[
https://issues.apache.org/jira/browse/AXIS2-6061?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17929070#comment-17929070
]
Manfred Weiss edited comment on AXIS2-6061 at 2/21/25 8:46 AM:
---------------------------------------------------------------
It simply makes no sense to expect a SOAP envelope with an HTTP-404. Without
the fix, 404 errors can unfortunately no longer be recognised as such.
The PR fixes the error and the test.
was (Author: mweiss):
It simply makes no sense to expect a SOAP envelope with an HTTP-404. Without
the fix, 404 errors can unfortunately no longer be recognised as such.
> 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: [email protected]
For additional commands, e-mail: [email protected]
