There are a couple of things happening here. First, the Xalan homepage[1] has the following to say about catalogs -
"The Xalan comman[d]-line transformation program does not deploy an OASIS catalog or perform other security measures. URLs are resolved using the system directory of the local machine and DNS to resolve host locations." and also "A future release of the Xalan command-line transformation program may include support for an OASIS entity resolver catalog." So, if the DTDs and XSDs aren't in your system directory, Xalan will fetch them from the network every time they're needed. Second, the W3C actively tries to discourage that kind of program behavior, and have configured their webservers to return errors under certain circumstances in order to try to curb it. [2],[3] In fact, my testing for this bug had results very similar to [3] - I was able to fetch the DTD from my browser or via wget with no problems. But trying to do it from Xerces or Xalan failed consistently. Just to be sure, I then put a copy of the DTDs on one of my servers and updated the xhtml doctype to reference that location instead, and Xalan worked as expected, even with the remote DTDs. So this doesn't appear to be a defect, but rather, a missing feature. As such, I'm switching the severity to "wishlist" [1] https://xalan.apache.org/xalan-c/ [2] http://www.w3.org/blog/systeam/2008/02/08/w3c_s_excessive_dtd_traffic/ [3] http://lists.w3.org/Archives/Public/site-comments/2010Nov/0017.html
signature.asc
Description: Digital signature
