[
https://issues.apache.org/jira/browse/SOLR-15923?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17482796#comment-17482796
]
Shawn Heisey commented on SOLR-15923:
-------------------------------------
[~epugh] Just got a look at what your change does.
Built the 9.0 snapshot .tgz file. Extracted it, added SOLR_JETTY_HOST=0.0.0.0
to include file, started, created a core. Went to base URL for core. Although
it is a little better, it's still basically an error page. A user that is
trying out the base URL they're putting into their application config is still
likely to conclude that the URL is wrong.
I think the base URL should not return a 404. It should return a special page
that indicates success contacting the base URL for that core/collection. Maybe
something like the following:
{code:java}
This is the base URL for the index named foo. It is the correct URL to give to
many applications that access Solr.
{code}
That seems a little too spartan, but I couldn't think of the right wording to
add more.
A 404 error would be the right thing to send in response to accessing a handler
that doesn't exist. [http://localhost:8983/solr/foo/unknown] as an example.
> 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
> Assignee: David Eric Pugh
> Priority: Minor
> Fix For: 9.1
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> 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-unsubscr...@solr.apache.org
For additional commands, e-mail: issues-h...@solr.apache.org
