[ 
https://issues.apache.org/jira/browse/SOLR-9000?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15445622#comment-15445622
 ] 

Jan Høydahl commented on SOLR-9000:
-----------------------------------

-1 to support this now that Solr is a standalone app and being a servlet is 
just an impl. detail.
Lots of Solr config relies on the fact that there is only one Solr in the 
container, such as the use of Java properties for {{solr.solr.home}}, 
{{solr.data.dir}} etc.
We should close this with "Won't fix". 

I will probably be easier to achieve embedding Solr in various ways once we 
re-package Solr and get rid of the Jetty coupling we have today.

> 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]

Reply via email to