[
https://issues.apache.org/jira/browse/SOLR-545?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Henri Biestro updated SOLR-545:
-------------------------------
Attachment: solr-545.patch
About the fall-through behavior of the filter, the default/example Jetty
configuration still declares the (deprecated) servlet.
The net effect is that hitting 'http://.../select' (instead of
http://.../corename/select') still works since the servlet will use the
SolrCore.getCore() to find a core.
As a tentative workaround, this small patch introduces the SolrDispatchFilter
'strict' parameter.
If 'strict' is set to true, the filter will not fall through the chain and thus
disallow any other filter/servlet to handle the request.
By default, if unspecified, the filter is 'strict' in multicore and lenient
(not strict) in 'single core'.
> remove MultiCore "default" core / cleanup DispatchHandler
> ---------------------------------------------------------
>
> Key: SOLR-545
> URL: https://issues.apache.org/jira/browse/SOLR-545
> Project: Solr
> Issue Type: Bug
> Affects Versions: 1.3
> Reporter: Ryan McKinley
> Assignee: Ryan McKinley
> Fix For: 1.3
>
> Attachments: solr-545.patch
>
>
> MultiCore should require a core name in the URL. If the core name is
> missing, there should be a 404, not a valid core. That is:
> http://localhost:8983/solr/select?q=*:* should return 404.
> While we are at it, we should cleanup the DispatchHandler. Perhaps the best
> approach is to treat single core as multicore with only one core? As is the
> tangle of potential paths is ugly.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
