rgoers commented on issue #252: Fixed message length with TLS and Syslog // fixes LOG4J2-2532 URL: https://github.com/apache/logging-log4j2/pull/252#issuecomment-454093120 It isn't documented correctly. The only doc for it is at http://logging.apache.org/log4j/2.x/log4j-core/apidocs/org/apache/logging/log4j/core/layout/Rfc5424Layout.html#createLayout(org.apache.logging.log4j.core.net.Facility,%20java.lang.String,%20int,%20boolean,%20java.lang.String,%20java.lang.String,%20java.lang.String,%20boolean,%20java.lang.String,%20java.lang.String,%20java.lang.String,%20java.lang.String,%20java.lang.String,%20java.lang.String,%20java.lang.String,%20boolean,%20org.apache.logging.log4j.core.layout.LoggerFields[],%20org.apache.logging.log4j.core.config.Configuration) and I don't believe even that is correct. As I recall, either syslog-ng or rsyslog accepts a message length prefix to allow you to have multi-line messages. I don't think this option really has anything to do with TLS but I am not sure. This was added in https://issues.apache.org/jira/browse/LOG4J2-338, so it has nothing to do with RFC-5424.
---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: [email protected] With regards, Apache Git Services
