Uploaded image for project: 'Magnolia Multisite Module'
  1. Magnolia Multisite Module
  2. MULTISITE-72

MultiSiteFilter doesn't set site correctly in the AggregationState after a forward

    XMLWordPrintable

Details

    • Bug
    • Resolution: Unresolved
    • Major
    • None
    • 1.2.5
    • None

    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).

      Checklists

        Acceptance criteria

        Attachments

          Activity

            People

              Unassigned Unassigned
              bvass Bence Vass
              Votes:
              1 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:

                Checklists

                  Bug DoR
                  Task DoD