Skip to content
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

Static HTML in demos still refer to Jetty 10/11 and earlier concepts. #12768

Closed
joakime opened this issue Feb 5, 2025 · 0 comments · Fixed by #12770
Closed

Static HTML in demos still refer to Jetty 10/11 and earlier concepts. #12768

joakime opened this issue Feb 5, 2025 · 0 comments · Fixed by #12770
Assignees
Labels
Bug For general bugs on Jetty side

Comments

@joakime
Copy link
Contributor

joakime commented Feb 5, 2025

Jetty version(s)
12.0.16

Jetty Environment
All demos in all environments

Java version/vendor (use: java -version)
Any

OS type/version
Any

Description
While triaging issue #12767 it was noticed that the static HTML in the demos still refer to old concepts, versions, and directories.
This is bad/misleading and needs to be updated.

Examples, seen during ee10-demo-jetty #12767 (comment)

<h1>Welcome to Jetty 11 - REMOTE ACCESS!!</h1>
You can disable the remote address checking by editing demo-base/webapps/demo-jetty.d/demo-jetty-override-web.xml

We should review all of the static HTML for this kinds of forgotten updates.

@joakime joakime added the Bug For general bugs on Jetty side label Feb 5, 2025
@joakime joakime self-assigned this Feb 5, 2025
@joakime joakime moved this to 🏗 In progress in Jetty 12.0.17 - FROZEN Feb 5, 2025
joakime added a commit that referenced this issue Feb 6, 2025
…ferences

Issue #12768 - Cleanup references to old Jetty versions
@github-project-automation github-project-automation bot moved this from 🏗 In progress to ✅ Done in Jetty 12.0.17 - FROZEN Feb 6, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug For general bugs on Jetty side
Projects
Status: ✅ Done
Development

Successfully merging a pull request may close this issue.

1 participant