Fix FortiGate regex parsing fields #51
Open
Conversation
This file contains hidden or 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
…both patterns for quoted and unquoted values
…g the message if there's an invalid messge
|
There's also a "Invalid Fortigate syslog message" exception thrown if the log mesage contains a new line, because of the PRI_PATTERN regex, added a fix for that also. |
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.
Fix for Graylog2/graylog2-server#3854
Replaced existing KV_PATTERN and QUOTED_KV_PATTERN with a single regex reusing them with (?:|), it matches both quoted and unquoted fields and avoids creating erroneous fields when the log message has a URL filed like url="/test?field=value".