Uploaded image for project: 'Solr'
  1. Solr
  2. SOLR-9000

New Admin UI hardcodes /solr context and fails when it changes

Attach filesAttach ScreenshotVotersWatch issueWatchersCreate sub-taskLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    • Bug
    • Status: Closed
    • Major
    • Resolution: Won't Fix
    • 6.0
    • None
    • Admin UI
    • None

    Description

      If the solr context is changed from /solr to any other value (e.g. /solr6_0/instance/solr1), the new Admin UI does not work as it still tries to load resources from /solr prefix:

      The context is changed by editing server/contexts/solr-jetty-context.xml:

      <Set name="contextPath"><Property name="hostContext" default="/solr6_0/instance/solr1"/></Set>

      and by changing redirect in the server/etc/jetty.xml

      <New class="org.eclipse.jetty.rewrite.handler.RedirectRegexRule">
      <Set name="regex">^/$</Set>
      <Set name="replacement">/solr6_0/instance/solr1/</Set>
      </New>

      This affects New Admin UI, as well as both links between the UIs.

      The old Admin UI seems to work with the changed context, once it is manually loaded.

      Attachments

        Issue Links

        Activity

          This comment will be Viewable by All Users Viewable by All Users
          Cancel

          People

            arafalov Alexandre Rafalovitch
            arafalov Alexandre Rafalovitch
            Votes:
            1 Vote for this issue
            Watchers:
            7 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment