[
https://issues.apache.org/jira/browse/LOG4J2-3475?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17527236#comment-17527236
]
ASF subversion and git services commented on LOG4J2-3475:
---------------------------------------------------------
Commit 2db7968d56b75ec6bdba2176a8d63ffb683ef3d7 in logging-log4j2's branch
refs/heads/master from Jeremy Lin
[ https://gitbox.apache.org/repos/asf?p=logging-log4j2.git;h=2db7968d56 ]
[LOG4J2-3475] Add missing message parameterization in RegexFilter
Conflicts:
log4j-core/src/test/java/org/apache/logging/log4j/core/filter/RegexFilterTest.java
> RegexFilter does not respect useRawMsg option in some cases
> -----------------------------------------------------------
>
> Key: LOG4J2-3475
> URL: https://issues.apache.org/jira/browse/LOG4J2-3475
> Project: Log4j 2
> Issue Type: Bug
> Components: Filters
> Affects Versions: 2.17.2
> Reporter: Jeremy Lin
> Priority: Major
> Fix For: 2.17.3
>
>
> [https://github.com/apache/logging-log4j2/blob/rel/2.17.2/log4j-core/src/main/java/org/apache/logging/log4j/core/filter/RegexFilter.java#L58-L61:]
> {code:java}
> public Result filter(final Logger logger, final Level level, final Marker
> marker, final String msg,
> final Object... params) {
> return filter(msg);
> }
> {code}
> This code does not parameterize the message when {{useRawMsg}} is false.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
