Details
-
Improvement
-
Status: Closed
-
Minor
-
Resolution: Fixed
-
None
-
None
-
None
Description
When accessing the base URL for a core, Solr returns a 404 error. For example, browsing to http://localhost:8983/solr/dovecot on my install returns a short html page:
HTTP ERROR 404 Not Found
URI: | /solr/dovecot |
---|---|
STATUS: | 404 |
MESSAGE: | Not Found |
SERVLET: | default |
I believe that it is Jetty generating this page.
I've heard from more than one user that when they see this, they think their Solr install is broken.
I believe that the base URL for a core should display something that lets a user know that the core they tried to access is indeed functional, but that they need more stuff on the URL for it to actually do anything. I haven't tried this with a collection on SolrCloud, but I assume that also returns a 404. One thing that some might think of for this that I think we should NOT do is have that URL redirect to the admin UI page for the core. If we do that, some users might assume that they have to update the base URL in their application to the admin UI URL that comes up, which will not work.
Attachments
Issue Links
- links to