logging-log4j-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Scott Severtson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (LOG4J2-136) Syslog: Optional escaping of newlines in message body
Date Fri, 21 Dec 2012 19:35:12 GMT

    [ https://issues.apache.org/jira/browse/LOG4J2-136?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13538333#comment-13538333

Scott Severtson commented on LOG4J2-136:

BTW, if you work with rsyslog, the logical newline escape string is "\012", which is compatible
with how rsyslog escapes other control characters.
> Syslog: Optional escaping of newlines in message body
> -----------------------------------------------------
>                 Key: LOG4J2-136
>                 URL: https://issues.apache.org/jira/browse/LOG4J2-136
>             Project: Log4j 2
>          Issue Type: Improvement
>          Components: Appenders, Layouts
>    Affects Versions: 2.0-beta3
>         Environment: N/A
>            Reporter: Scott Severtson
>            Priority: Minor
>              Labels: patch
>             Fix For: 2.0-beta4
>         Attachments: syslog-escape-newlines.patch
> Syslog (both RFC-3164 and 5424) use newline characters to frame messages. As Log4J2 messages
may include newlines in the message body, it is necessary to replace newlines with a configurable
escape string.
> I've implemented a configuration option "newLineEscape" which accepts a replacement string.
The default is to not escape newlines (i.e. current behavior).

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org

View raw message