Community
Participate
Working Groups
w3.org has restricted the access to it's site from java clients. See: http://www.w3.org/2005/06/blog/systeam/2008/02/08/w3c_s_excessive_dtd_traffic So whenever ValBuilderJob tries to open connection to w3.org the connection and the job stalls for 30 sec, which can cause significant slowdown. Problem is explained in detail here: http://www.vineetmanohar.com/2010/11/w3-org-dtds-blocked-from-java-http-500/
Created attachment 196217 [details] fix The plugin org.eclipse.wst.standard.schemas contributes loose.dtd and strict.dtd to the XML catalog, but in case the public id in a n xml header is different from "-//W3C//DTD HTML 4.01 Transitional//EN" the validation doesn't use the local dtd files. This patch add both dtds in the XML catalog as URIs
org.eclipse.wst.standard.schemas is in Source Editing. This looks like something that was overlooked that can boost our performance.
I am not doubting it, but is surprising we'd missed this all these years. I know years ago, we tried to find all code that might have been accessing w3.org. So ... I'm wondering ... what kind of file is this? Is it named "xml" by any chance? But using HTML? Doesn't really matter (fix should still be made) but, I'd recommend testing with HTML, XHTML, and XML. I know for some of the HTMLs, we purposely do not use the DTDs to validate, but have "built in" content models via Java code. And chance you are working with a "reduced" set of plugins? And maybe have left out HTML ones? At any rate, thanks for reporting ... sounds important.
Looks appropriate to me. Adding project lead for review.
Code released. Thanks for the patch.
