You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@lucene.apache.org by "Alexandre Rafalovitch (Jira)" <ji...@apache.org> on 2019/10/07 01:24:00 UTC
[jira] [Closed] (SOLR-428) Restrict valid RequestHandler names
[ https://issues.apache.org/jira/browse/SOLR-428?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Alexandre Rafalovitch closed SOLR-428.
--------------------------------------
Long resolved. Marking closed for completeness.
> Restrict valid RequestHandler names
> -----------------------------------
>
> Key: SOLR-428
> URL: https://issues.apache.org/jira/browse/SOLR-428
> Project: Solr
> Issue Type: Improvement
> Affects Versions: 1.3
> Reporter: Ryan McKinley
> Priority: Minor
> Attachments: SOLR-428-HanderNameRestriction.patch
>
>
> In SOLR-350, we added support for multiple cores. To access each core, you send a request to:
> http://host:port/context/@core0/handlerpath - uses core0
> http://host:port/context/@core1/handlerpath - uses core1
> This is fine unless a hander is registered to the a name that starts with '@'
> I think we should make a rule that the 1st character has to be a letter or digit. This will give us room to treat other leading punctuation as a key token.
> Perhaps it is not fair to add this restriction after 1.2, but it is (hopefully) a rare case so not a big deal. I guess we could add a configurable flag to not check this condition...
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@lucene.apache.org
For additional commands, e-mail: issues-help@lucene.apache.org