Don't Automatically Prettify JSON Data in Log #101
Comments
|
Took a look again at this a few months ago, the catch at the moment of the removal of auth related tokens is done at the object level that happens from the parse and then reformatting. So for safety sake, there needs to be some other sorta filtering done that would provide the same protection for the logs. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Prettifying JSON data for the log is nice, but there should at least be a way to turn it off since it can cause the data to change.
For example, you can post content that looks like this:
but it will be logged as:
This can cause problems if you have a bug on your server but you spend all your time trying to debug the client because you have a log "proving" that's where the problem is.
The text was updated successfully, but these errors were encountered: