[
https://issues.apache.org/jira/browse/SOLR-9054?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Valerio Di Cagno updated SOLR-9054:
-----------------------------------
Description:
(Edited)
If Apache Solr 6.0 is started without using the default context root "/solr"
every admin service will not work properly and is not possible to use the
provided links to go back to the old GUI.
In the javascript files sometimes the parameter config.solr_path is ignored
or replaced with the value /solr returning 404 on access.
Affected files: solr-webapp/webapp/js/services.js
Suggested solution: Complete the integration with /js/scripts/app.js
Some common use case which should be considered:
- Different version of Solr coexist in the same host.
- Sometimes users have no direct access to the hosts but must use a proxied
gateway (to interact with an external authentication system)
- A common practice is to hide internal hosts between an alias when behind a
load balancer.
"server.org/app1", "server.org/app2" and "server.org/app3" may actually be
running 3 different machines, but the user should not care about it.
was:
If Apache Solr 6.0 is started without using the default context root "/solr"
every admin service will not work properly and is not possible to use the
provided links to go back to the old GUI.
In the javascript files sometimes the parameter config.solr_path is ignored
or replaced with the value /solr returning 404 on access.
Affected files:
solr-webapp/webapp/js/services.js
Suggested solution:
Complete the integration with /js/scripts/app.js
> The new GUI is using hardcoded paths
> ------------------------------------
>
> Key: SOLR-9054
> URL: https://issues.apache.org/jira/browse/SOLR-9054
> Project: Solr
> Issue Type: Bug
> Components: web gui
> Affects Versions: 6.0
> Reporter: Valerio Di Cagno
>
> (Edited)
> If Apache Solr 6.0 is started without using the default context root "/solr"
> every admin service will not work properly and is not possible to use the
> provided links to go back to the old GUI.
> In the javascript files sometimes the parameter config.solr_path is ignored
> or replaced with the value /solr returning 404 on access.
> Affected files: solr-webapp/webapp/js/services.js
> Suggested solution: Complete the integration with /js/scripts/app.js
> Some common use case which should be considered:
> - Different version of Solr coexist in the same host.
> - Sometimes users have no direct access to the hosts but must use a proxied
> gateway (to interact with an external authentication system)
> - A common practice is to hide internal hosts between an alias when behind a
> load balancer.
> "server.org/app1", "server.org/app2" and "server.org/app3" may actually
> be running 3 different machines, but the user should not care about it.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
