[
https://issues.apache.org/jira/browse/SOLR-8058?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14747032#comment-14747032
]
Hoss Man commented on SOLR-8058:
--------------------------------
i think the patch prefix check is a safer bet: 1) it's simpler; 2) it doesn't
risk false negatives if someone uses something like the ShowFileRequestHandler
to serve a .html file from the config set.
if we can consolidate all of the admin UI resources into a single root dir then
great, but as long as they are confined to a _fixed_ set of dirs it shouldn't
matter (and moving them around now is just an added complexity / risk to try
and get into a bug fix)
> Collections that start with css*, js*, img*, and tpl* can't be accessed as
> they match the exclusion filter
> ----------------------------------------------------------------------------------------------------------
>
> Key: SOLR-8058
> URL: https://issues.apache.org/jira/browse/SOLR-8058
> Project: Solr
> Issue Type: Bug
> Affects Versions: 5.2, 5.2.1, 5.3, 5.3.1
> Reporter: Anshum Gupta
> Assignee: Anshum Gupta
> Priority: Blocker
> Attachments: SOLR-8058.patch
>
>
> Collections that match css*, js*, img*, and tpl* can't be reached as the SDF
> short circuits paths that match those regular expressions.
> It should have only short circuited exact matches for those directories i.e.
> \css/*,/js/*,/img/*,/tpl/* but that doesn't seem to be the case.
> Need to fix this regular expression so that the collection can be reached.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
