On Wednesday 01 July 2009 10:39:38 Karen Tracey wrote: > I'm guessing, then, that you mean you could see the password in the > traceback local arguments? I don't think that's a bug, as I don't think > there's any attempt to hide/suppress "sensitive" information in the local > variable data. (In general, how would the filtering code be able to > identify what counts as "sensitive"?) If you happen to hit a case where a > "sensitive" setting has been stashed in a local variable, it'll be visible > on the DEBUG page. (DEBUG=True is really not meant for production.)
yes, it was in local variable data. Unfortunately I had set DEBUG=True in the production environment for a minute as the auth failure was due to something specific to the production server and I needed the error message. -- regards kg http://lawgon.livejournal.com --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
