You are viewing a plain text version of this content. The canonical link for it is here.
Posted to c-dev@xerces.apache.org by "Scott Cantor (JIRA)" <xe...@xml.apache.org> on 2016/06/10 01:50:21 UTC
[jira] [Commented] (XERCESC-2070) Ability to disable DTD processing
[ https://issues.apache.org/jira/browse/XERCESC-2070?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15323729#comment-15323729 ]
Scott Cantor commented on XERCESC-2070:
---------------------------------------
r1747620
XERCES_DISABLE_DTD set to "1" will cause the scanner to report a fatal error if a DTD is seen. Existing applications won't see any change.
As I said, I would supplement this with a feature in the parser on trunk, and just deprecate the variable.
> Ability to disable DTD processing
> ---------------------------------
>
> Key: XERCESC-2070
> URL: https://issues.apache.org/jira/browse/XERCESC-2070
> Project: Xerces-C++
> Issue Type: Improvement
> Components: Validating Parser (DTD)
> Reporter: Scott Cantor
> Fix For: 3.2.0, 3.1.4
>
>
> We should provide a way for applications that don't need DTDs to be insulated from bugs in that code.
> Trunk could do this pretty easily with the same property URI that Xerces-J and Java use for this.
> To do it without an ABI change, I'm going to patch in an environment variable check. It's ugly, but this is a problem of such magnitude that I don't see any other option, particularly given the lack of resources devoted to the project.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: c-dev-unsubscribe@xerces.apache.org
For additional commands, e-mail: c-dev-help@xerces.apache.org