[
https://issues.apache.org/jira/browse/SOLR-7240?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14359691#comment-14359691
]
Ramkumar Aiyengar commented on SOLR-7240:
-----------------------------------------
Re: your comment on having /solr so that we could have an incompatible /v2 in
the future: wouldn't the same concern apply to the redirect as well? I.e. what
API is the root url going to service during such an API shift? It leads to the
root URL being on the oldest version if it stays on v1, but if always redirect
it to v2, we are waiving off all backward compatibility requirements for the
root url alone -- how do we communicate this discrepancy in compatibility
guarantees between the two URLs? And how useful is it going to be if we say
that the meaning of the redirect is going to change under your feet without
notice?
> redirect / to /solr
> --------------------
>
> Key: SOLR-7240
> URL: https://issues.apache.org/jira/browse/SOLR-7240
> Project: Solr
> Issue Type: Improvement
> Reporter: Hoss Man
> Attachments: SOLR-7240.patch
>
>
> Prior to Solr 5, we avoided doing anything fancy with our jetty configs
> because we didn't want to overly customize "the example" beyond things that
> involved loading the solr.war.
> That's not longer an issue, so we might as well plop in some jetty config
> features to redirect / to /solr.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
