support JSON logging #1208
Merged
support JSON logging #1208
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
This was referenced Mar 15, 2017
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.
Adds
escapeattribute to theaccess-logconfiguration directives. The attribute takes one of the two values:apache,json.apacheis the default.If the value is
json, the escape sequence changes from\xNNto\u00NN, and the special value used for logging missing values is changed from-tonull.Note: Regarding the escape sequence, the reason for using
\u00NNis that it is impossible to assume that the input (e.g. URL) is UTF-8. Therefore, we treat it as ISO-8859-1 in order to preserve the original octets. Users with the knowledge of the application should convert the strings to appropriate encoding laterwards, if required.