hi, after i've read this blog post:
http://superjared.com/entry/urgent-upgrade-django-if-deployed-fastcgi/ i also became a little nervous because i also have a fastcgi-backed website. but the problem is, i am unable to reproduce this problem. actually i use a custom fastcgi script ( the fastcgi.py wasn't there in django when i needed it ), which looks like this: ============================= import os import sys sys.path.extend(....<paths>...) from flup.server.fcgi_fork import WSGIServer from django.core.handlers.wsgi import WSGIHandler os.environ['DJANGO_SETTINGS_MODULE'] = '<settings-module-name>' WSGIServer(WSGIHandler()).run() ============================== and whatever i try (doing an "1/0" in a view, configuring settings.py to a non-existent database..), django respects the DEBUG setting in settings.py. if it's set to True, i get detailed error messages, and if it's set to False, then i do not get them. so could maybe someone explain if i am also vulnerable and have to change my script, or not? thanks, gabor --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-developers?hl=en -~----------~----~----~----~------~----~------~--~---
