When requesting an URI that starts with the handle of an URI2RepositoryMapping, result is 404, because the mapping will prefix the URI internally with the exact same handle (URI now contains the handle twice). This results in Magnolia not being able to find the node, e.g. for the demo:
http://localhost:8080/travel will internally try to resolve /travel/travel → 404
The cause is
MAGNOLIA-6882 and the removal of the infamous maybeHandle-check, which would check whether given handle would actually exist in given repository and if not, would try to remove the double-up-handle.
Unless the URI2RepositoryMapping has a URIPrefix defined, requesting the root-node (or any other subnode) should internally be handled correctly.