[
https://jira.jboss.org/jira/browse/JBIDE-4686?page=com.atlassian.jira.plu...
]
Victor Rubezhny commented on JBIDE-4686:
----------------------------------------
The situation is a little bit strange for me... The pointed DTD is defined in XML Catalog,
and the XML Catalog in its turn is used by the resolver to get the DTD's location.
So, I see the only one reason of the issue reproduced by Julien Kronegg - is some problem
with WTP WST version/installation (for example for some reason there is no -//W3C//DTD
XHTML 1.0 Transitional//EN DTD defined in the XML Catalog in Julien's environment).
I'm ready to commit a code of DTD resolver that searchs for the DTDs and Schemas in an
alternate way for the WST-defined ones.
Is it really needed?
"Server returned HTTP response code: 503" warning during
HTML/XHTML validation
------------------------------------------------------------------------------
Key: JBIDE-4686
URL:
https://jira.jboss.org/jira/browse/JBIDE-4686
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Cleanup, Seam
Affects Versions: 3.1.0.M2
Reporter: Alex Savitsky
Assignee: Viacheslav Kabanovich
Priority: Blocker
Fix For: 3.1.0.M3
All HTML/XHTML files are validated with a warning "Server returned HTTP response
code: 503 for URL:
http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd". W3C site
(the one that hosts the referenced XHTML/HTML DTDs) has the following explanation:
http://www.w3.org/blog/systeam/2008/02/08/w3c_s_excessive_dtd_traffic. Basically, they now
block IPs for machines that request their DTDs too often, and recommend to cache the DTD
instead of requesting it every time. Apparently, the JBoss Tools validator is one of the
affected ones.
The solution is simple - please cache the DTDs, given that they're highly unlikely to
EVER change.
Upd: affects M2 version of JBoss Tools as well, not just M1
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira