[
https://issues.apache.org/jira/browse/SOLR-4431?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13596596#comment-13596596
]
Hoss Man commented on SOLR-4431:
--------------------------------
bq. If there's some internal important structural reason for "/solr", "#" and
"~cloud" sections, perhaps each would need to be addressed.
The crux of the "/#/" URL schema is because these are all UI based URLs, and
the UI is a single html page bound to the "/" URL, with jquery hooks to have
the browser look at the URL fragment (everything after the "#") do decide which
views/info to show (in the case of the example, solr us registered in the
"/solr" context, so the ui is bound to "/solr/"
Having the entire UI be powered by the single "/" URL means that it's very
clear when a request is for the UI vs a request to underlying
collections+handlers.
switching these UI URLs from things like "/~cloud" to "/cloud" would cause
problems for anyone who might want to have a collection named "cloud"
Personally, i don't see any major need to change the UI URLs. I would rather
the UI urls be a little longer if it means ensuring no conflicts with the
underlying API URIs.
i can certainly understand how the curb appeal might be improved by switching
the jetty example to run solr in the root context ("/" instead of "/solr", with
some jetty redirect magic so old example URLs take you to the right place) by
default but i don't see any reason to sweat the "#" or "~"
> Developer Curb Appeal: easier URL to get to Cloud UI
> ----------------------------------------------------
>
> Key: SOLR-4431
> URL: https://issues.apache.org/jira/browse/SOLR-4431
> Project: Solr
> Issue Type: Improvement
> Components: SolrCloud
> Affects Versions: 4.1
> Reporter: Mark Bennett
> Fix For: 4.2
>
>
> Currently the URL to get the cloud UI is
> http://172.16.10.236:8983/solr/#/~cloud
> The path and anchor portion is very strange: "/solr/#/~cloud"
> Ideally it would just be "/cloud"
> Or even just "/", and if it's in "cloud mode", take the admin to the right
> place.
> If there's some internal important structural reason for "/solr", "#" and
> "~cloud" sections, perhaps each would need to be addressed.
> Another option would be to possibly put something the default Jetty xml file
> to handle this as some type of redirect or registered handle.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
