[jira] Commented: (XMLCOMMONS-61) Please make catalog use default instead of an afterthough

classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view

[jira] Commented: (XMLCOMMONS-61) Please make catalog use default instead of an afterthough

JIRA jira@apache.org

    [ https://issues.apache.org/jira/browse/XMLCOMMONS-61?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12969518#action_12969518 ]

Ted Guild commented on XMLCOMMONS-61:


I'm surprised to get a response after 2 years and 10 months since filling this bug report :)  Thank you for replying.

It would be great if Xalan and Xerces came with a XML catalog by default like many XML processing libraries do.  Yes one can add this after but since it is optional and not there from the start the vast majority of instances do not use the tools you mention.

We have blocked (HTTP 503, TCP), tarpitted and have made efforts to educate yet the traffic just grows (I've seen peaks at half a billion a day).

As maintaining a catalog to include additional schemata for emerging XML formats is tedious the suggestion is to have resolver write these to the catalog, a caching catalog.

We also recently started talking to JDK engineers to see if  they can't do this upstream for all XML libraries.

> Please make catalog use default instead of an afterthough
> ---------------------------------------------------------
>                 Key: XMLCOMMONS-61
>                 URL: https://issues.apache.org/jira/browse/XMLCOMMONS-61
>             Project: XmlCommons
>          Issue Type: Bug
>          Components: XML Commons Resolver
>    Affects Versions: XML Commons Resolver 1.2.0
>         Environment: Operating System: other
> Platform: Other
> URL: http://xerces.apache.org/xerces2-j/faq-xcatalogs.html
>            Reporter: Ted Guild
>            Assignee: Commons Developers Mailing List
> W3C gets an immense amount of DTD traffic with user-agent often only identifying
> itself as Python or Java.  
> http://www.w3.org/blog/systeam/2008/02/08/w3c_s_excessive_dtd_traffic
> In a number of cases we have heard back from people affected by our automated
> blocking indicating they are running Xalan and/or Xerces doing such things as
> validating XML or doing XSL transforms.  We have directed some we have been in
> correspondence with to your catalog instructions.
> http://xerces.apache.org/xerces2-j/faq-xcatalogs.html
> The vast majority of Xalan/Xerces installations most likely do not implement
> catalogs nor caching of external DTDs and other schemata. It would seem the
> resolver does not care about HTTP response codes nor caching directives.
> http://www.ietf.org/rfc/rfc2616.txt
> Better than a default catalog would be a caching XML Catalog resolver as I
> understand is part of Glassfish
> http://norman.walsh.name/2007/09/07/treadLightly
> There are other Java libraries contributing to this traffic as well. Xalan and
> Xerces are widely used, important libraries.  Your assistance in reducing this
> excessive traffic to W3C and others hosting standards schemata would be greatly
> appreciated.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]