[jboss-jira] [JBoss JIRA] (LOGMGR-98) Disable UTF-8 BOM in syslog handler when encoding is undefined

[David Lloyd (JIRA)]

    [ https://issues.jboss.org/browse/LOGMGR-98?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12948816#comment-12948816 ] 

David Lloyd commented on LOGMGR-98:
-----------------------------------

If the platform encoding is UTF-8, this will definitely cause confusion.
                
> Disable UTF-8 BOM in syslog handler when encoding is undefined
> --------------------------------------------------------------
>
>                 Key: LOGMGR-98
>                 URL: https://issues.jboss.org/browse/LOGMGR-98
>             Project: JBoss Log Manager
>          Issue Type: Enhancement
>      Security Level: Public(Everyone can see) 
>            Reporter: Kyle Lape
>            Assignee: James Perkins
>
> Section 6.4 MSG: http://tools.ietf.org/html/rfc5424#section-6.4
> bq. If a syslog application encodes MSG in UTF-8, the string MUST start with the Unicode byte order mask (BOM), which for UTF-8 is ABNF %xEF.BB.BF.  The syslog application MUST encode in the "shortest form" and MAY use any valid UTF-8 sequence.
> While we want to conform to the spec, it is desirable to not include the BOM in some practical applications, e.g. rsyslog does not strip the BOM, and sometimes it would be easier to be able to configure JBoss to not include the BOM than to configure rsyslog to drop it.
> Perhaps we can not include the BOM is the encoding is undefined for the {{SyslogHandler}}, but do include it if the {{encoding}} is explicitly set to {{UTF-8}}.

--
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