-
Bug
-
Resolution: Fixed
-
Neutral
-
5.4.11, 5.5.1
-
None
-
None
-
-
Empty show more show less
-
Basel 97
-
3
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
Source of the problem
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.
Desired behavior
Unless the URI2RepositoryMapping has a URIPrefix defined, requesting the root-node (or any other subnode) should internally be handled correctly.
- caused by
-
MAGNOLIA-6882 Remove legacy code that allows to access site with duplicate prefix in the url
- Closed
- is causing
-
MAGNOLIA-7131 URI2RepositoryMapping cleans URI too eagerly
- Closed
-
MAGNOLIA-7166 Page gets 404 when the beginning of the requested path matches handle prefix in site definition
- Closed
- is depended upon by
-
MULTISITE-71 Multisite serves the root page only if the site definition name matches the handlePrefix
- Closed