List of bugs that are fixed in Microsoft XML 3.0 Service Pack 5

Problems that are fixed in MXSML 3.0 SP5

• Fixes for failures that may occur during low memory conditions.
• Fixes for memory leak issues.
• Performance enhancements that are related to the internal treatment of spin locks and critical section caching.
• Fixes for problems that occur in high-stress situations.
• Fixes for problems that occur while an MSXML application is running under Application Verifier.
• Fixes for security issues. These issues include enhancing security for XMLHTTP host header spoofing and denial-of-service attacks for applications that except XML files that may contain many attributes.

• Applications may stop responding when a document is saved to itself. For example, this problem occurs when you use the save method to save a file to itself as shown in the following code:

  xmldoc.save(xmldoc)

• A problem that occurs when a node from one Document Object Model (DOM) document is copied to another DOM document. For example, assume that you have node <NX> in a read-only DOM document and node <NY> in a read/write DOM document. This problem occurs if you clone the <NX> node, and you try to append the <NX> node to the <NY> node. This situation is shown in the following code:

  NY.appendChild( NX.cloneNode(true))
  

• Cached XML files generate unnecessary HTTP GET requests for embedded XML/Extensible Stylesheet Language for Transformation (XSLT) files. For example, if you load an .xml file that contains an .xsl file that refers to another .xml file, the referenced files are refreshed even though the .xml file was cached.

• The XMLHTTP object crashes when multiples of 4092 bytes of data are sent by using the send method.

• A memory leak and a security problem occur in XMLHTTP code if credentials are required when the send method is called.

• Included .xsl files are not downloaded. This problem occurs because MSXML 3.0 performs HTTP POST requests instead of GET requests for the included files.

• Redirects to relative pages return an "Unspecified Error" error message when the ServerXMLHTTP send method is called.

• XMLHTTP has problems when it translates responses that include multi-byte characters.

• The AllowDocumentFunction property returns the incorrect value. This property was added in MSXML 3.0 SP4.

• The EBay Turbo Lister application crashes because of an Extensible Stylesheet Language (XSL) problem in MSXML 3.0 SP4. The problem occurs when many nodes are transformed under stress.

New features that are included in MSXML 3.0 SP5

A Simple API for XML (SAX) parser property that is named "prohibit-dtd" is added

• false (VARIANT_FALSE) = (default) Allow a document type definition (DTD) to be included in an XML document
• true (VARIANT_TRUE) = Prohibit a DTD from being included in an XML document

A DOM property that is named "ProhibitDTD" is added

xmldoc.setProperty("ProhibitDTD", True); // Jscript
xmldoc.setProperty "ProhibitDTD", True   'VBScript

dom1.load("file with DTD");
dom2.setProperty("ProhibitDTD", true);
dom2.Load(dom1);   <--- This will Error

The IXMLParser::SetFlags method allows a new flag that is named XMLFLAG_PROHIBIT_DTD

A new interface that is named IXMLParser3 is added

interface IXMLParser3 : IXMLParser2
{
    HRESULT SetProperty(
        [in] const WCHAR* pwcName,
        [in] VARIANT value);
 
    HRESULT GetProperty(
        [in] const WCHAR* pwcName,
        [out,retval] VARIANT* value);
};

pParser->SetProperty(L"max-attributes-per-element" , value )
                                 /*value is VARIANT containing a LONG*/