[
https://issues.apache.org/jira/browse/SOLR-18041?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18047802#comment-18047802
]
ASF subversion and git services commented on SOLR-18041:
--------------------------------------------------------
Commit 58e11d8457f51a52e31267cc7b942cdd0a10c5f5 in solr's branch
refs/heads/main from Gus Heck
[ https://gitbox.apache.org/repos/asf?p=solr.git;h=58e11d8457f ]
SOLR-18041 PathExclusionFilter extracted from SolrDispatchFilter (#3981)
Collects and simplify all path exclusion logic into a single class configured
in web.xml and makes our reliance on jetty's DefaultServlet (or whatever is
configured with the name 'default') for serving static content explicit rather
than an implicit feature one has to figure out (or already know about).
> Do path exclusions in a separate filter.
> ----------------------------------------
>
> Key: SOLR-18041
> URL: https://issues.apache.org/jira/browse/SOLR-18041
> Project: Solr
> Issue Type: Sub-task
> Components: Server
> Reporter: Gus Heck
> Priority: Minor
> Labels: pull-request-available
> Time Spent: 1.5h
> Remaining Estimate: 0h
>
> One of the simplest things to pull out of SolrDispatchFilter is the path
> exclusion logic. What this logic does is it looks for static resources that
> need to be served (mostly for the UI) and ensures that they pass through
> SolrDispatchFilter.
> At some point if the auth stuff get's moved to a filter then we could think
> about if any of this stuff should be inside auth, and easily have 2 filters
> one inside and one outside.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
