-
Notifications
You must be signed in to change notification settings - Fork 4.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Missing new line between JSON access log entries #5018
Comments
cc @aa-stripe |
Thanks for reporting this! I'll take a look |
This is indeed the case, can't believe I missed this, me--. Working on a patch now! |
htuch
pushed a commit
that referenced
this issue
Nov 14, 2018
Tack a newline onto the end of all JSON access log lines Risk Level: Low Testing: Every JSON unit test will now check to see that there is one (and only one) newline in a log line Docs Changes: None Release Notes: None Fixes #5018 Signed-off-by: Aaltan Ahmad <[email protected]>
fredlas
pushed a commit
to fredlas/envoy
that referenced
this issue
Mar 5, 2019
Tack a newline onto the end of all JSON access log lines Risk Level: Low Testing: Every JSON unit test will now check to see that there is one (and only one) newline in a log line Docs Changes: None Release Notes: None Fixes envoyproxy#5018 Signed-off-by: Aaltan Ahmad <[email protected]> Signed-off-by: Fred Douglas <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Missing new line between JSON access log entries
Description:
Config:
Sample Listener config:
The text was updated successfully, but these errors were encountered: