You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@logging.apache.org by "ASF subversion and git services (Jira)" <ji...@apache.org> on 2021/01/14 16:29:00 UTC
[jira] [Commented] (LOG4J2-2998) JsonWriter truncation doesn't take
surrogates into account
[ https://issues.apache.org/jira/browse/LOG4J2-2998?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17264997#comment-17264997 ]
ASF subversion and git services commented on LOG4J2-2998:
---------------------------------------------------------
Commit cef32ec3e46bc80dd6fd2bb89ec8b6467060ab51 in logging-log4j2's branch refs/heads/LOG4J2-2998 from Volkan Yazici
[ https://gitbox.apache.org/repos/asf?p=logging-log4j2.git;h=cef32ec ]
LOG4J2-2998 Fix truncation of excessive strings ending with a high surrogate in JsonWriter.
> JsonWriter truncation doesn't take surrogates into account
> ----------------------------------------------------------
>
> Key: LOG4J2-2998
> URL: https://issues.apache.org/jira/browse/LOG4J2-2998
> Project: Log4j 2
> Issue Type: Bug
> Components: JsonTemplateLayout
> Affects Versions: 2.14.0
> Reporter: Volkan Yazici
> Assignee: Volkan Yazici
> Priority: Major
> Fix For: 2.14.1
>
>
> {{JsonWriter}} of {{JsonTemplateLayout}} works on {{char}}\-by\-{{char}} basis, even while truncating excessive input. This approach might leave the truncated string in a state such that the last {{char}} (which will be followed by {{truncatedStringSuffix}}) might be the high surrogate of a surrogate pair. This incomplete {{char}} needs to be removed.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)