Uploaded image for project: 'SiteMesh'
  1. SiteMesh
  2. MSITEMESH-39

Magnolia calls external URL when rendering dynamic area

    Details

    • Type: Improvement
    • Status: Closed
    • Priority: Neutral
    • Resolution: Duplicate
    • Affects Version/s: 1.0.1
    • Fix Version/s: None
    • Labels:
      None

      Description

      When magnolia renders page accessed via Multisite domain specified name, dynamic components are also fetched by request issued to domain URL. That makes internal magnolia page rendering mechanism dependent on domain URL which can point to external server e.g. load balancer, which does not seems to be right approach. Further if the multisite page is accessed with mappings/website/ URIPrefix specified, the dynamic component is fetched with domainName but the URIPrefix is not taken into account when build component URL. That makes the url generated for dynamic content requesting load balancer with path which is not supported. Is it a bug or there is a possibility to reconfigure magnolia to fetch dynamic content via localhost?

      Example scenario

      Multisite settings:

      • Sitename: "casino.com"
      • URIPrefix: "/online-casino/v2"
      • handlePrefix: "/casino-com"
      • domains/casino.com/name: "web-rainbow-six.tipdev.com"

      "header" area in "casino-com" node set as dynamic area for caching

      When page is requested from a user's browser as follows:

      NOTE: GET request is done internally by Magnolia and not by the user's browser, this was checked from logs

      Expected behaviour is as follows:

      In our case this is a problem because web-rainbow-six.tipdev.com is our loadbalancer and not the server Magnolia is running on

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                rkovarik Roman Kovařík
                Reporter:
                msmirnou mikalai smirnou
              • Votes:
                0 Vote for this issue
                Watchers:
                3 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved:
                  Date of First Response: