You are viewing a plain text version of this content. The canonical link for it is here.
Posted to c-dev@axis.apache.org by ax...@ws.apache.org on 2004/10/22 21:13:26 UTC
[jira] Updated: (AXISCPP-222) infinite loop in XMLPaserExpat when it encounters bad XML
The following issue has been updated:
Updater: James Guido (mailto:james_guido@homedepot.com)
Date: Fri, 22 Oct 2004 12:12 PM
Changes:
Attachment changed to XMLParserExpat.cpp.diff_w_v1.9
---------------------------------------------------------------------
For a full history of the issue, see:
http://issues.apache.org/jira/browse/AXISCPP-222?page=history
---------------------------------------------------------------------
View the issue:
http://issues.apache.org/jira/browse/AXISCPP-222
Here is an overview of the issue:
---------------------------------------------------------------------
Key: AXISCPP-222
Summary: infinite loop in XMLPaserExpat when it encounters bad XML
Type: Bug
Status: Unassigned
Priority: Minor
Project: Axis-C++
Components:
XML parser abstraction layer
Versions:
1.2 Final
1.3 Beta
Assignee:
Reporter: James Guido
Created: Fri, 22 Oct 2004 12:12 PM
Updated: Fri, 22 Oct 2004 12:12 PM
Environment: HP-UX with GCC compiler, Expat 1.95.7
Description:
Code when encounters only one event in XML events stack, it checks if last event is CHAR data. If last event is CHAR data; then, code proceeds to parse more data. Infinite loop is triggered when CHAR is the last data in stream. Eventhough stream returns TRANSPORT_FINISHED, XMLParserExpat goes into an infinite loop requesting for more data to parse.
I accidently trigger the bug by setting the content-lenght smaller than message, then the web server clipped SOAP message. If Axis w/ Expat parser encounters a message that was clipped/truncated, it will go into infinite if CHAR data is last data in stream.
I am attaching the fix I used.
---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira