[
https://issues.apache.org/jira/browse/SOLR-18168?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18070700#comment-18070700
]
ASF subversion and git services commented on SOLR-18168:
--------------------------------------------------------
Commit 00e0870c4d50a6020f1a9039722b376741e569b8 in solr's branch
refs/heads/main from David Smiley
[ https://gitbox.apache.org/repos/asf?p=solr.git;h=00e0870c4d5 ]
SOLR-18168: Remove PathExclusionFilter; serve static content via
ResourceServlet (#4243)
Instead of using a bespoke PathExclusionFilter to short-circuit Solr's filter
chain
for Admin UI static resources (/css/*, /js/*, /img/*, /partials/*, etc.),
web.xml now
maps those paths directly to Jetty's built-in ResourceServlet. Solr's filters
are
remapped from url-pattern="/*" to servlet-name="SolrServlet", so they naturally
apply
only to Solr requests and bypass static resources without bespoke code.
BATS integration tests were added to replace ones that had used JettySolrRunner
previously.
Co-authored-by: copilot-swe-agent[bot]
<[email protected]>
Co-authored-by: dsmiley <[email protected]>
> Replace PathExclusionFilter with web.xml configuration
> ------------------------------------------------------
>
> Key: SOLR-18168
> URL: https://issues.apache.org/jira/browse/SOLR-18168
> Project: Solr
> Issue Type: Improvement
> Components: Server
> Reporter: David Smiley
> Assignee: David Smiley
> Priority: Minor
> Labels: pull-request-available
> Time Spent: 1.5h
> Remaining Estimate: 0h
>
> Now that SolrServlet exists (a Servlet), we are unblocked from removing
> PathExclusionFilter. Instead, its task can be accomplished with web.xml
> configuration. Furthermore, admin UI serving should be exclusively tested
> with BATS (integration) -- JettySolrRunner can be simpler.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
