You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@solr.apache.org by "David Eric Pugh (Jira)" <ji...@apache.org> on 2022/01/13 17:48:00 UTC

[jira] [Commented] (SOLR-15923) Base URL for a core returns 404

    [ https://issues.apache.org/jira/browse/SOLR-15923?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17475567#comment-17475567 ] 

David Eric Pugh commented on SOLR-15923:
----------------------------------------

SolrCloud does the same thing: http://chorus.dev.o19s.com:8983/solr/ecommerce/

Oh, and so does http://chorus.dev.o19s.com:8983/solr/ecommerce/bob

Do you have thoughts on what should happen?   Should a Solr specific message show up that points you to the Admin tool?  Or, just a Solr specific page but with the same content?  As in, it isn't a generic Jetty/Servlet error, but instead something that lets you know Solr is working.


> Base URL for a core returns 404
> -------------------------------
>
>                 Key: SOLR-15923
>                 URL: https://issues.apache.org/jira/browse/SOLR-15923
>             Project: Solr
>          Issue Type: Improvement
>      Security Level: Public(Default Security Level. Issues are Public) 
>            Reporter: Shawn Heisey
>            Priority: Minor
>
> 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:
> h2. 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.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@solr.apache.org
For additional commands, e-mail: issues-help@solr.apache.org