#3707: Log 500 errors to file when in production
------------------------------------------+---------------------------------
Reporter: yary h <[EMAIL PROTECTED]> | Owner: adrian
Status: new | Component: Core
framework
Version: SVN | Resolution:
Keywords: error log | Stage: Design
decision needed
Has_patch: 0 | Needs_docs: 0
Needs_tests: 0 | Needs_better_patch: 0
------------------------------------------+---------------------------------
Comment (by ubernostrum):
Unfortunately, I don't think we can afford to work around every
conceivable setup; the web server log is where this data should end up,
and (on a couple sites I just checked) does end up under both
Apache/mod_python and lighttpd/FastCGI. Unless there's something I'm
missing here, I'm inclined to mark this wontfix and keep responsibility
for proper logging on the web server's side of things.
--
Ticket URL: <http://code.djangoproject.com/ticket/3707#comment:3>
Django Code <http://code.djangoproject.com/>
The web framework for perfectionists with deadlines
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en
-~----------~----~----~----~------~----~------~--~---
