Hi,
On Tue, 26 Jan 2016 20:35:53 +0100
Milan Krčmář <milan.krc...@gmail.com> wrote:
> why does the to_syslog_ietf() replace line breaks ('\r','\n') in
> message text with space (' ')? [in nx_logdata_to_syslog_rfc5424(),
> almost at the end]
That's done because linebreaks represent the end-of-record when syslog is
transferred over TCP or TLS/SSL.
> In RFC5424, the message text is allowed to contain any octets.
This is what RFC5424 says:
"6.4. MSG
The syslog application SHOULD avoid octet values below 32 (the
traditional US-ASCII control character range except DEL). These
values are legal, but a syslog application MAY modify these
characters upon reception. For example, it might change them into an
escape sequence (e.g., value 0 may be changed to "\0"). "
> The IETF standard
> allows the line breaks to appear in structured data fields as well -
> these are preserved. So, in output, you might get line breaks in
> middle of whole event anyway.
This might need to be reviewed to protect against such issues.
Regards,
Botond
------------------------------------------------------------------------------
Site24x7 APM Insight: Get Deep Visibility into Application Performance
APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
Monitor end-to-end web transactions and take corrective actions now
Troubleshoot faster and improve end-user experience. Signup Now!
http://pubads.g.doubleclick.net/gampad/clk?id=267308311&iu=/4140
_______________________________________________
nxlog-ce-users mailing list
nxlog-ce-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nxlog-ce-users
