[MULTISITE-72] MultiSiteFilter doesn't set site correctly in the AggregationState after a forward Created: 30/May/17  Updated: 30/May/17

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

Type: Bug Priority: Major
Reporter: Bence Vass Assignee: Unassigned
Resolution: Unresolved Votes: 1
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

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   

MultiSiteFilter sets the site with a call to aggregationState.setSite(site);

After a forward (f.e. by a 404 virtualURIMapping) it uses the same site set before ( Site site = aggregationState.getSite(); ).

If the forward was to another site (of the same domain), the new site is not correctly set in the AggregationSate, leading to several issues (f.e. URIMapping issues)

This is a big problem, if 2 sites use the same domain, but one has a URIPrefix
f.e.:
www.domain.com
www.domain.com/en

a 404 forward to an error.html will not work in this case, because Magnolia will look for node /en/error in the wrong site (instead of /error in the correct one).


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