[
https://issues.apache.org/jira/browse/SOLR-9584?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15814594#comment-15814594
]
Jan Høydahl commented on SOLR-9584:
-----------------------------------
I think I agree more with this change. Proxying Solr behind nginx or something
should be possible even if the path is different from /solr/.
Have you tested your patch? Have you checked whether other parts of Admin UI
also has hardcoded /solr/ paths?
> The absolute URL path in server/solr-webapp/webapp/js/angular/services.js
> would make context customization not work
> -------------------------------------------------------------------------------------------------------------------
>
> Key: SOLR-9584
> URL: https://issues.apache.org/jira/browse/SOLR-9584
> Project: Solr
> Issue Type: Improvement
> Security Level: Public(Default Security Level. Issues are Public)
> Components: UI
> Affects Versions: 6.2
> Reporter: Yun Jie Zhou
> Priority: Minor
> Labels: patch
>
> The absolute path starting from /solr in
> server/solr-webapp/webapp/js/angular/services.js would make the context
> customization not work.
> For example, we should use $resource('admin/info/system', {"wt":"json",
> "_":Date.now()}); instead of $resource('/solr/admin/info/system',
> {"wt":"json", "_":Date.now()});
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
