[MULTISITE-83] Language handling with MultiSite should be more strict Created: 14/Feb/18  Updated: 23/Sep/19

Status: Open
Project: Magnolia Multisite Module
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Improvement Priority: Neutral
Reporter: Jaroslav Simak Assignee: Unassigned
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
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)
Date of First Response:

 Description   

When using MultiSite together with I18nContentSupport, one can access language mutations multiple ways:
If /travel/mappings/website@URIPrefix=/test

then one can access site using
https://demopublic.magnolia-cms.com/de/test/contact
https://demopublic.magnolia-cms.com/test/de/contact

In both cases MultiSite removes the URIPrefix and language is then resolved by the I18nContentSupport.

Same can happen if we use site prefix, for example these will also work:
https://demopublic.magnolia-cms.com/de/sportstation/about
https://demopublic.magnolia-cms.com/sportstation/de/about
(Note: enable i18n in sportstation and remove domain mapping for travel site before clicking urls above.)

Same as above, in both cases MultiSite removes the site prefix and language is then resolved by the I18nContentSupport.

I'd consider good practice to support only the first case as it seems confusing that we can access same content under two same urls.


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