[
https://issues.apache.org/jira/browse/LOG4J2-3326?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17471994#comment-17471994
]
ASF subversion and git services commented on LOG4J2-3326:
---------------------------------------------------------
Commit 01e38b528d9ec5d64f15c4ba5ae2a94105998a82 in logging-log4j2's branch
refs/heads/master from Gary Gregory
[ https://gitbox.apache.org/repos/asf?p=logging-log4j2.git;h=01e38b5 ]
[LOG4J2-3326] Log4j 1.2 bridge fixes parsing filters in properties
configuration file #680.
> Log4j 1.2 bridge not parsing filters from Properties configuration properly
> ---------------------------------------------------------------------------
>
> Key: LOG4J2-3326
> URL: https://issues.apache.org/jira/browse/LOG4J2-3326
> Project: Log4j 2
> Issue Type: Improvement
> Components: log4j 1.2 emulation
> Affects Versions: 2.17.1
> Reporter: Benjamin Röhl
> Assignee: Gary D. Gregory
> Priority: Major
>
> h2. Status Quo
> The log4j 1.2 bridge gives backward-compatiblilty for the following filters,
> based on [migration
> documentation|https://logging.apache.org/log4j/2.x/manual/migration.html]:
> {code:java}
> Supported Filters include: DenyAllFilter, LevelMatchFilter, LevelRangeFilter,
> StringMatchFilter.{code}
> h2. Problem
> The filters' parameters are not parsed properly, and instead fallback to
> default configuration for filter.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
