This is an automated email from the ASF dual-hosted git repository.

ckozak pushed a commit to branch release-2.x
in repository https://gitbox.apache.org/repos/asf/logging-log4j2.git

commit 7eccaa4fb27511827bb44f6c845e9b3fb2a93bf6
Author: Ralph Goers <[email protected]>
AuthorDate: Fri Dec 17 16:20:03 2021 -0700

    Fix bug in template
---
 src/site/markdown/index.md.vm | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/src/site/markdown/index.md.vm b/src/site/markdown/index.md.vm
index 400ced9..b96e581 100644
--- a/src/site/markdown/index.md.vm
+++ b/src/site/markdown/index.md.vm
@@ -46,9 +46,9 @@ From version 2.17.0 (for Java 8), only lookup strings in 
configuration are expan
 in any other usage, only the top-level lookup is resolved, and any nested 
lookups are not resolved.
 
 In prior releases this issue can be mitigated by ensuring your logging 
configuration does the following:
-* Replace Context Lookups like `$${ctx:loginId}` in PatternLayout with Thread 
Context Map patterns (%X, %mdc, or %MDC)
+* Replace Context Lookups like `${dollar}${dollar}{ctx:loginId}` in 
PatternLayout with Thread Context Map patterns (%X, %mdc, or %MDC)
   in the logging configuration.
-* Remove refrences to Context Lookups like `$${ctx:loginId}` in the 
configuration where they originate
+* Remove refrences to Context Lookups like `${dollar}${dollar}{ctx:loginId}` 
in the configuration where they originate
   from sources external to the application such as HTTP headers or user input.
 
 $h4 Reference

Reply via email to