Allow version '0' for structured syslog messages #3503
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Althought RFC 5424 clearly states that '1' is the only valid version for structured syslog messages, some syslog daemons are using '0' as a version identifier. https://tools.ietf.org/html/rfc5424#section-9.1 Fixes #3502
|
This also has to be back-ported into |
dennisoelkers
approved these changes
Feb 16, 2017
dennisoelkers
pushed a commit
that referenced
this pull request
Feb 16, 2017
Althought RFC 5424 clearly states that '1' is the only valid version for structured syslog messages, some syslog daemons are using '0' as a version identifier. https://tools.ietf.org/html/rfc5424#section-9.1 Fixes #3502 (cherry picked from commit af1a258)
Closed
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Although RFC 5424 clearly states that '1' is the only valid version for structured syslog
messages, some syslog daemons are using '0' as a version identifier.
https://tools.ietf.org/html/rfc5424#section-9.1
Fixes #3502