Joakim Erdfelt

Also, Jetty 11 is now at End of Community Support. See: * #10485 Please upgrade to Jetty 12.

Also of note, that the Specification (and Java) puts an additional requirement on "HostName" in that it must be a Fully Qualified DNS Hostname. The spec (and java) require that...

Opened PR #11580 to start this issue. Currently just a cherry-pick of commit fed10f79aacecfcb4118bcbe39fcb21d98666f25 along with some testcase updates

Yeah, sorry, my mind was stuck on the exception message from the old PR ... https://github.com/jetty/jetty.project/blob/fed10f79aacecfcb4118bcbe39fcb21d98666f25/jetty-core/jetty-http/src/main/java/org/eclipse/jetty/http/HttpURI.java#L1460-L1461 The exception messages from that commit showed up as ... ``` HTTP/1.1 400 Bad...

Jetty 11 is now at End of Community Support * #10485 You should be using Jetty 12 at this point in time. Also note that your version, 11.0.17 is subject...

Looks like you are talking about path parameters, and on-again / off-again niche concept that gets no love in the URL/URI/HTTP specs. It causes all sorts of problems in the...

Note: the `logging.properties` for `java.util.logging` is not auto-discovered, auto-loaded by java itself. You have to write code to find and load that file (unlike literally every other java logging framework...

Configuring logging should be handled differently than configuring other aspects of the application. Having logging initialized early (as early in the JVM as possible) is the best decision with logging....

With logback, you can do this . See http://logback.qos.ch/manual/appenders.html#RollingFileAppender There's 2 ways to do this ... **Using separate rolling & triggering policies:** What you'll setup is a `rollingPolicy` which is...

Wait, the webapp's WEB-INF dir? Do we want to have the webapp's logging punch a hole through the WebApp isolation layers? (ie: WebAppClassloader) I would strongly discourage this behavior, as...