[Tracker-discuss] [issue434] ProgrammingError revealing server info

Retro metatracker at psf.upfronthosting.co.za
Mon Jan 23 21:23:06 CET 2012


New submission from Retro <mamatijekurba at gmail.com>:

I wanted to delete a patch set that I have uploaded to a Python issue reporting portal @ http://bugs.python.org, but I got a

"ProgrammingError at /review/13816/patchset/4039/delete
schema "datetime" does not exist"

and got all the Django nitty-gritty info about the Python server. This is not good because someone can misuse that information. Please fix this. The "DEBUG = True" is set and so all the details about the Python server is out on the open. Better change that to "DEBUG = False" and let the user get a standard 500 error page instead.

It says at the bottom: "You're seeing this error because you have DEBUG = True in your Django settings file. Change that to False, and Django will display a standard 500 page."

And, of course, fix the ProgrammingError so that the option "Delete Patch Set" would work. :)

----------
messages: 2369
nosy: Retro
priority: critical
status: unread
title: ProgrammingError revealing server info

_______________________________________________________
PSF Meta Tracker <metatracker at psf.upfronthosting.co.za>
<http://psf.upfronthosting.co.za/roundup/meta/issue434>
_______________________________________________________


More information about the Tracker-discuss mailing list