Prevent sensative information from being logged

[wwsean08]

This change uses the SafeExceptionReportFilter when logging the body as outlined in issue #64 and also fixes #64. I have done some basic testing with a simple django application which uses the sensitive_post_parameters decorator and seen that the fields are filtered out.

One caveat is that this does change the behavior of logging the body, the decorator that specifies the variables to filter doesn't run until the view is called so logging the body needs to come after self.get_response( request ) otherwise it'll still have sensitive information in plaintest. Here's an example of what I get using this now on an application using allauth

{'csrfmiddlewaretoken': 'xAXmfqD1PYMttgqseguGHh1FQxWPkhxVPu07BHvXA9MICiNtSJJbU1pXrkfzVTFr', 'login': '[email protected]', 'password': '********************', 'next': '/'}

Previously the password would have been revealed. Also because SafeExceptionReportFilter is based on request.POST instead of request.body I have left a fallback in case that doesn't exist, I don't think that'll ever get hit though.

[tclancy]

@wwsean08 or @kennethjiang can you submit a PR either backing this out or fixing #67 ?

[kennethjiang]

Sorry for missing your question earlier @tclancy . Not sure about @wwsean08 but I can't reproduce the problem mentioned in #67

[tclancy]

There's a test case to do it in the ticket.

[wwsean08]

I'll look into #67 tonight and see if i can come up with a fix for the test case as I never ran into that during my testing.