Uploaded image for project: 'Search Engine Optimization'
  1. Search Engine Optimization
  2. SEO-32

Consolidate / simplify fetcher configuration

    XMLWordPrintable

Details

    • Bug
    • Resolution: Unresolved
    • Neutral
    • None
    • None
    • None

    Description

      Auditors that use a fetcher to retrieve a rendered page each have an individually configured fetcher. There are many auditors using fetchers in the default bootstrapped configuration.

      The configured HTTP fetchers probably won't work out of the box after installation: they assume Magnolia is running at http://localhost:8080 in the root context. Many HTTP fetcher configuration may have to be changed.

      The HTTP fetcher configuration allows retrieval with personas to test personalization scenarios. 

      Possibilities to consider: 

      • Move fetcher configuration to module, auditors reference fetcher configuration by name
      • Change bootstrapped fetcher configuration to use rendering fetchers instead of HTTP fetchers
      • Change HTTP fetchers to use system base URL if no URL is configured
      • Change fetcher configuration to reference one HTTP fetcher

      Checklists

        Acceptance criteria

        Attachments

          Activity

            People

              awarinner Andrew Warinner
              awarinner Andrew Warinner
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated:

                Checklists

                  Bug DoR
                  Task DoD