If true, it does seem like a bug. Could you provide a test for Django's test suite or a sample project to reproduce it?
On Thursday, September 15, 2016 at 6:53:55 AM UTC-4, Ben Whale wrote: > > Hi > > What I'd like to do is log the request body whenever the django.request > logger logs something. I had assumed that the extra context referred to as > request in > https://docs.djangoproject.com/en/1.10/topics/logging/#django-request was > something like an HTTPRequest object. It is, however, an instance > of socket._socketobject. > > Is it possible to get data for logging using the socket? For example the > get parameters, the post data, any information associated to a file that > was sent like what every has been read out of the socket? What about the > request headers? > > Why is a socket passed to the logger? I must admit that I assume this to > be a bug. The user has a very limited way of interacting with the socket > via the string formatting syntax and the methods of the socket (as > introspected via dir) don't lend them selves to this form of access. > > I'm currently using django 1.10 if that helps. > > Thanks for any help. > > > -- You received this message because you are subscribed to the Google Groups "Django users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/django-users. To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/496538d2-10fe-426c-835d-e311422a959c%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
