lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jan Høydahl (JIRA) <>
Subject [jira] [Commented] (SOLR-9000) New Admin UI hardcodes /solr context and fails when it changes
Date Mon, 09 Jan 2017 16:58:58 GMT


Jan Høydahl commented on SOLR-9000:

That is not true. You can start as many Solrs you like on the same host by specifying different
ports {{solr start -p <port>}}

> New Admin UI hardcodes /solr context and fails when it changes
> --------------------------------------------------------------
>                 Key: SOLR-9000
>                 URL:
>             Project: Solr
>          Issue Type: Bug
>          Components: UI
>    Affects Versions: 6.0
>            Reporter: Alexandre Rafalovitch
>            Assignee: Alexandre Rafalovitch
>         Attachments: solr-wrong-urls-screenshot.png
> 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:
>  bq. <Set name="contextPath"><Property name="hostContext" default="/solr6_0/instance/solr1"/></Set>
> and by changing redirect in the server/etc/jetty.xml
> {quote}
>     <New class="org.eclipse.jetty.rewrite.handler.RedirectRegexRule">
>       <Set name="regex">^/$</Set>
>       <Set name="replacement">/solr6_0/instance/solr1/</Set>
>      </New>
> {quote}
> 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.

This message was sent by Atlassian JIRA

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message