[
https://issues.apache.org/jira/browse/SOLR-8058?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14745911#comment-14745911
]
Upayavira commented on SOLR-8058:
---------------------------------
I'm not quite sure what that code is trying to do. The Angular UI adds
/partials to the list of directories, and it works just fine. Looking at the
regexp entries, they are broken anyway:
<init-param>
<param-name>excludePatterns</param-name>
<param-value>/css/*,/js/*,/img/*,/tpl/*</param-value>
</init-param>
That says any value that starts with /css, then is followed by a sequence of
zero or more forward slashes. I think what is intended is /css/.*, no?
Why do we need these excluded patterns?
> 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
>
> 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: [email protected]
For additional commands, e-mail: [email protected]
