Yeah I have done that, but without changing anything in xjetty, many buttons like editing of pages in XWIKI responses in http instead of https (if I understood the issue correctly).
As referenced in the tomcat documentation:
If you are using another server as a HTTPS proxy (such as Nginx, Apache httpd or HAProxy), follow the instructions below to avoid unexpected errors (such as “failed to lock page”).
Or explaned here: Message “failed to lock the page” when tring to edit a page - Help / Discuss - XWiki Forum
- If using HTTPS for accessing XWiki, several modifications have to be made to ensure proper functionality. Since urls are generated from relative path (/xwiki/bin/show/Space/Page), Tomcat has to know which protocol to use, otherwise JSON requests with redirect fails (attachment uploads, extension updating, etc.)
This is the exact problem and for tomcat some small things have to be configured (and after setting them the “failed to lock page” and similar errors are gone) so I guess the same is necessary for xjetty too - the question is where and how.