GitHub user kshchepanovskyi opened a pull request:

    https://github.com/apache/logging-log4j2/pull/147

    LOG4J2-2032 Curly braces in parameters should not be treated as placeholders

    https://issues.apache.org/jira/browse/LOG4J2-2032
    
    When logging event parameter contains two consecutive opening and
    closing curly braces - for example {} in the middle of parameter,
    they should not be treated as a placeholder.

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/kshchepanovskyi/logging-log4j2 
fix/double-placeholder-processing

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/logging-log4j2/pull/147.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #147
    
----
commit b68f797ea01e669fc4b4c630cd7a96e14f4cc6ef
Author: Kostiantyn Shchepanovskyi <kostiantyn.shchepanovskyi@...>
Date:   2018-02-06T10:20:35Z

    LOG4J2-2032 Fix SslConfigurationTest running on Windows behind proxy
    
    Corporate proxies might not allow connection to external resources.

commit 3814afe7d81ed065b1ecb3e593547c32d4536ddd
Author: Kostiantyn Shchepanovskyi <kostiantyn.shchepanovskyi@...>
Date:   2018-02-06T11:26:00Z

    LOG4J2-2032 Curly braces in parameters should not be treated as placeholders
    
    When logging event parameter contains two consecutive opening and
    closing curly braces - for example {} in the middle of parameter,
    they should not be treated as a placeholder.

----


---

Reply via email to