DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<
http://issues.apache.org/bugzilla/show_bug.cgi?id=44426>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=44426 Summary: Please make catalog use default instead of an
afterthough
Product: XmlCommons
Version: 1.x
Platform: Other
URL:
http://xerces.apache.org/xerces2-j/faq-xcatalogs.html OS/Version: other
Status: NEW
Keywords: ErrorMessage, XSLTBug, Xerces2, RFC
Severity: normal
Priority: P2
Component: Resolver
AssignedTo:
commons-dev@...
ReportedBy:
ted@...
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_trafficIn 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.htmlThe 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.txtBetter 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/treadLightlyThere 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.
--
Configure bugmail:
http://issues.apache.org/bugzilla/userprefs.cgi?tab=email------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
