Vincent Massol

Knowing that this used to work in Jetty 10, maybe there's been a change in Jetty 12?

If I remove our `xwiki.ini` and try to regenerate it with `java --add-opens java.base/java.lang=ALL-UNNAMED --add-opens java.base/java.io=ALL-UNNAMED --add-opens java.base/java.util=ALL-UNNAMED --add-opens java.base/java.util.concurrent=ALL-UNNAMED -Djava.io.tmpdir=./tmp -Djetty.home=jetty -Djetty.base=. -Dfile.encoding=UTF8 -Djetty.http.port=8080 -jar jetty/start.jar --add-modules=xwiki jetty.http.port=8080 STOP.KEY=xwiki...

Thanks @joakime for the recommendations. However, this shouldn't affect why the `jetty.httpConfig.uriCompliance=RFC3986,AMBIGUOUS_PATH_ENCODING` property in `startd.d/xwiki/ini` isn't used in `etc/jetty.xml` to replace `` in ``, right? This is what I got...

> I don't know why they're listed as "ee8" properties and if that has some importance or not: Probably because `xwiki.ini` is the match for `xwiki.mod` which has: ``` [environment]...

Thanks @joakime I've now removed the following from `xwiki.mod` and the properties from `xwiki.ini` are now defined as core and thus the `jetty.httpConfig.uriCompliance` property is seen from `jetty.xml`: ``` [environment]...

Only remaining question I guess is whether there's a syntax to force a property to be defined as core?

Thanks @joakime

@janbartel Thanks a lot for the additional explanations! So far I've removed the `ee8` environment from my [`xwiki.mod`](https://github.com/xwiki/xwiki-platform/commit/3447bac26faadf5d4f93b60e9ab283fed1927fbd#diff-779bef223c9f91542f4672199edec98a93ba428ff1f119748758e7fb548df005L24-L26). I could add it back and instead add a `servet.ini` file in...

Thanks for the heads up @mojavelinux FTR, on the XWiki side we use java so we would need some java version to try it out/provide feedback/help. Have a great weekend.