-
Notifications
You must be signed in to change notification settings - Fork 1.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
If jetty.org is down, impossible to start Jetty server (12.0.5) - multiple dtd to eclipse and jetty #12403
Comments
Note: XML in webapps with links to eclipse.dev
was working (after removing those with https://jetty.org/configure_10_0.dtd) |
The existence or not of I'll test this out and see if a fix is necessary for jetty-12.0.x HEAD. Btw, you should upgrade to Jetty 12.0.14, you are missing several fixes for various security advisories. |
The XML which failed, was a "org.eclipse.jetty.fcgi.proxy.FastCGIProxyHandler" one:
it may perhaps help you to reproduce |
That looks wrong, I need to double check. |
It comes from here: https://jetty.org/docs/jetty/12/operations-guide/protocols/index.html#fcgi-configure |
That PUBLIC definition isn't registered in the xml catalog. It should read ... <!DOCTYPE Configure PUBLIC "-//Jetty//Configure//EN" "https://jetty.org/configure_10_0.dtd"> |
This URI/URL worked for months ... just not while jetty.org was down If I change in the dtd jetty.org to jetty.or, removing the 'g', I can reproduce the problem. I mean like that:
|
Removing the Can you run this and report back the output?
Feel free to overwrite sensitive things with |
|
You have nothing configured in your Are you using the Your stacktrace shows that you are using Jetty's
|
* The XmlConfiguration instance should not use an XML parser from the classloader. As that XML parser can be broken when it comes to XML entity resolution behaviors. (We always want local entity resolution, never external) Switching to SAXParserFactory.newDefaultInstance() ensures this behavior that we want/need. * More unit tests for behavior.
A simple test of your scenario ... First, make sure that any requests to a host
Now, lets configure a fresh
Lets add an XML with the Mortbay style of XML PUBLIC Id.
Double check the configuration to make sure that this XML is loaded.
Yup, it's listed on the Active XMLs entry. Now lets run with this odd XML, and double check that the internal references for XML entities are indeed pulled from the XML catalog we ship with, and not going to external entity sources. This call should fail in the same way that the OP reported, as
It works, without error. Looking closely at the behaviors, I can see that our |
Sorry for late reply. Here is the right --list-config
|
About the test with system's hosts and jetty.org to a false IP I tried, and yes, it's reproduced: but with another error java.net.UnknownHostException: jetty.org with 0.0.0.0
With 192.168.88.99: Connection timed out
|
Jetty version(s)
jetty-12.0.5
Jetty Environment
ee10
Java version/vendor
(use: java -version)
openjdk 17.0.9 2023-10-17
OS type/version
Linux or Windows
Description
xml in webapps, like
While https://jetty.org/ is down, I got error
How to reproduce?
Shutdown jetty.org ? ;)
The text was updated successfully, but these errors were encountered: