I've implemented new redirect module and make it default on / with redirection to /dashboard. That should resolve this issue.

I had to slightly modify requestUri calculation (see RedirectServlet) as code for X-Forward-Prefix was not behaving correctly for redirects for /favicon.ico. Please review if my changes are correct.

IndexModule is now disabled, but I was wondering if we shouldn't just move it.

As for adding advanced menu, I can work on that, but I wanted to confirm that current behavior is correct. Also, dashboard is not only for admins, so I wonder who should see this advanced menu, or if we should point/link to /index/ path with IndexModule being deployed there?

I've implemented new redirect module and make it default on / with redirection to /dashboard. That should resolve this issue.

Works like a charm

I had to slightly modify requestUri calculation (see RedirectServlet) as code for X-Forward-Prefix was not behaving correctly for redirects for /favicon.ico. Please review if my changes are correct.

The substring? Seems fine.

IndexModule is now disabled, but I was wondering if we shouldn't just move it.

Hmm... could be useful.

As for adding advanced menu, I can work on that, but I wanted to confirm that current behavior is correct. Also, dashboard is not only for admins, so I wonder who should see this advanced menu, or if we should point/link to /index/ path with IndexModule being deployed there?

In general previous behaviour with index listing everything even wasn't too good as it could expose regular user to "admin stuff".

Maybe, for now, to limit the scope (Dashboard could be improved in the future) just add a link to /index/ (that would maybe only be visible to admin users) in the left hand menu (below "Server info")?

I've applied changes in the recent commit.

Moved "index" to /index from /, added link in dashboard called "endpoints" on the sidebar (visible only to admin).

While working in this, I've encountered an issue with accessing Server info in the sidebar. Sometimes I got HTML web page and in some cases I've got JSON file. Results was always consistent and changed only when server was restarted.

I've narrowed it down to JaxRsRequestHandler::test(HttpServerRequest, String) implementation that was responsible for selecting method to run by checking if produced content type matches Accept header. As handlers were kept in Set and Accept header always at the end had */* it caused random method to be returned.

To solve that I've added a new method JaxRsRequestHandler::match(HttpServerRequest, String), that returns RequestHandlerMatcher which contains "handler, preference, and matcher (instead of just matcher) allowing us to gather RequestHandlerMatcher for all matching handlers and select the best one based on preference. That resolve the issue, but I've made a few minor changes (including deprecations) to make API more consistent.

Works great.