[MAGNOLIA-2064] 404 if a page has the same name as the webapp's context Created: 19/Feb/08  Updated: 23/Jan/13  Resolved: 03/Sep/08

Status: Closed
Project: Magnolia
Component/s: core
Affects Version/s: 3.5.4
Fix Version/s: 3.6.2, 3.6.3

Type: Bug Priority: Critical
Reporter: Magnolia International Assignee: Jan Haderka
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
duplicate
duplicates MAGNOLIA-2013 Pages with te same name as the servle... Closed
relation
is related to MAGNOLIA-2142 A page in top level which starts with... Closed
is related to MGNLDMS-126 DMS Module Makes Web Pages With "dms"... Closed
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

 Description   

This seems to be due to the fact that the I18nFilter further "decodes" the current URI, and the decode method removes the context path from the start of the given uri.
Changing this method might have undesired side effets.



 Comments   
Comment by Magnolia International [ 03/Jul/08 ]

If not related, this seems at least similar to MGNLDMS-126

Generated at Mon Feb 12 03:33:03 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.