[
https://issues.apache.org/jira/browse/AXIS2C-1475?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Lazarski resolved AXIS2C-1475.
-------------------------------------
Fix Version/s: 2.0.0
(was: 1.7.0)
Resolution: Implemented
This issue was implicitly resolved by the
AXIS2C-1628 fix in 2014. The issue was open since 2010 but the
underlying bug no longer exists in the current code base.
> Bad interaction between AXIS2_XML_PARSER_TYPE_BUFFER,
> axiom_soap_body_has_fault and XML escape sequence
> -------------------------------------------------------------------------------------------------------
>
> Key: AXIS2C-1475
> URL: https://issues.apache.org/jira/browse/AXIS2C-1475
> Project: Axis2-C
> Issue Type: Bug
> Components: guththila
> Affects Versions: 1.6.0
> Reporter: Sebastien Bigot
> Priority: Major
> Fix For: 2.0.0
>
>
> In order to check for soap Fault, I'm using the axiom_soap_body_has_fault
> with an axiom_xml_reader of kind AXIS2_XML_PARSER_TYPE_BUFFER.
> If the soap Body contains some XML escape sequences (&, <, ...), since
> the XML sequence escaping is done in place by the
> guththila_token_evaluate_references function, the Soap buffer is then
> corrupted.
> For example if the soap Body contains
> <urlAddress>http://test.net/application?event=callBack&pageid=test&flowId=justification&portletid=test&STATUS=OK</urlAddress>
> after the call to axiom_soap_body_has_fault , the buffer then contains:
> <urlAddress>http://test.net/application?event=callBack&pageid=test&flowId=justification&portletid=test&STATUS=OKst&STATUS=OK</urlAddress>
> which is bad.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
