[
https://issues.apache.org/jira/browse/SOLR-9000?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15814471#comment-15814471
]
Timo Hund commented on SOLR-9000:
---------------------------------
I know that the port can be used. And i also undestand an agree that solr
should be a blackbox which means that internally in the java application the
assumption is made that /solr is the path. What do you think about SOLR-9584? I
think this is something different because it is related to the use interface, a
proxy would not have a chance to change the delivered javascript code.
> New Admin UI hardcodes /solr context and fails when it changes
> --------------------------------------------------------------
>
> Key: SOLR-9000
> URL: https://issues.apache.org/jira/browse/SOLR-9000
> 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
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
