[MAGNOLIA-7040] When requesting an URI that starts with the handle of an URI2RepositoryMapping, result is 404 Created: 22/May/17  Updated: 28/Jun/18  Resolved: 24/May/17

Status: Closed
Project: Magnolia
Component/s: None
Affects Version/s: 5.4.11, 5.5.1
Fix Version/s: 5.4.13, 5.5.5

Type: Bug Priority: Neutral
Reporter: Philip Mundt Assignee: Philip Mundt
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
causality
caused by MAGNOLIA-6882 Remove legacy code that allows to acc... Closed
is causing MAGNOLIA-7131 URI2RepositoryMapping cleans URI too ... Closed
is causing MAGNOLIA-7166 Page gets 404 when the beginning of t... Closed
dependency
is depended upon by MULTISITE-71 Multisite serves the root page only i... Closed
relation
Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Bug DoR:
[ ]* Steps to reproduce, expected, and actual results filled
[ ]* Affected version filled
Date of First Response:
Sprint: Basel 97
Story Points: 3

 Description   

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.


Generated at Mon Feb 12 04:20:10 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.