README link is broken

[wendigo]

https://eclipse.dev/jetty/ redirects to https://jetty.org// which renders HTTP ERROR 400 Ambiguous URI empty segment 😢

[stephendnicholas]

I've just experienced a related issue where https://eclipse.dev/jetty/configure_10_0.dtd is redirecting to https://jetty.org//configure_10_0.dtd, which is causing a web app to fail to start up:

[joakime]

@stephendnicholas you have three things to address.

1. You are using an End of Community Support version of Jetty.

• EoCS (End of Community Support) for Jetty 10 / Jetty 11 - January 2024 #10485

• EoCS (End of Community Support) for Jetty 9 - June 2022 #7958

  You should be using a supported version of Jetty. Which is Jetty 12.0.x at this point in time.

2. you have something wrong with your jetty-xml jar, it shouldn't be going out onto the internet for the configure.dtd.

3. you have a XML that is referencing a 10.0 dtd, but are running a Jetty 9.4.49 version of Jetty (that will never work)

[jmcc0nn3ll]

I believe Eclipse is fixing the redirect. I'll post here when I get confirmation.

[stephendnicholas]

Thanks for the reply @joakime

I'm using the Eclipse Jetty integration (https://eclipse-jetty.github.io/) with its out of the box configuration, which I believe has 9.4 bundled inside, and specifies the 10.0 dtd automatically

I could probably look to reconfigure things to try and target a newer version of Jetty, which may then be configured differently, but I don't believe that's directly related to the issue here, and I just wanted to comment to give you a heads-up that the potential impact of this is larger than just a link in a readme (as I imagine a lot of people might be using the Eclipse integration in the same way I am)

[joakime]

@stephendnicholas that project is not run by the group here.

It's a standalone project with a different group of developers / committers.

[joakime]

@wendigo the redirect should be fixed.