You are viewing a plain text version of this content. The canonical link for it is here.
Posted to log4j-dev@logging.apache.org by "Ralph Goers (JIRA)" <ji...@apache.org> on 2013/05/30 19:17:21 UTC
[jira] [Resolved] (LOG4J2-263) RFC5424 Layout (and Syslog Layout)
uses platform encoding when no charset is specified in configuration
[ https://issues.apache.org/jira/browse/LOG4J2-263?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ralph Goers resolved LOG4J2-263.
--------------------------------
Resolution: Fixed
Fix Version/s: 2.0-beta7
RFC5424Layout has been fixed in revision 1487936 to not allow a charset to be specified. SyslogLayout still does as RFC 3164 does not restrict the message to a specific character set.
Please verify and close.
> RFC5424 Layout (and Syslog Layout) uses platform encoding when no charset is specified in configuration
> -------------------------------------------------------------------------------------------------------
>
> Key: LOG4J2-263
> URL: https://issues.apache.org/jira/browse/LOG4J2-263
> Project: Log4j 2
> Issue Type: Bug
> Components: Appenders, Core
> Affects Versions: 2.0-beta6
> Reporter: Remko Popma
> Fix For: 2.0-beta7
>
>
> RFC5424 seems to require UTF-8 or US-ASCII as the character encoding.
> Should the 'charset' attribute be removed so that this is no longer configurable?
> Is there any specification for the Syslog format?
> See also discussion here: https://issues.apache.org/jira/browse/LOG4J2-255?focusedCommentId=13659559&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13659559
--
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