Changes between Initial Version and Version 1 of Ticket #29571, comment 1
- Timestamp:
- Jul 18, 2018, 8:58:40 AM (6 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #29571, comment 1
initial v1 1 In production, the one serving your static files should be your web server not Django, and so the web server shou dl be in business of reporting 404 or other error.s1 In production, the one serving your static files should be your web server not Django, and so the web server should be in business of reporting 404 or other errors. 2 2 3 That, or there is some missing in your description of your setup.3 That, or there is some missing part in your description of your setup. 4 4 5 5 Generally speaking and following best practices, no Python code should be running as part of the request cycle for static assets. 6 6 7 Do you get any more details (full trac ceback, etc.) about the root reason for the 500 status error from email reporting? https://docs.djangoproject.com/en/2.0/howto/error-reporting/#server-errors7 Do you get any more details (full traceback, etc.) about the root reason for the 500 status error from email reporting? https://docs.djangoproject.com/en/2.0/howto/error-reporting/#server-errors 8 8 9 I'm closing , please reopen if you find the failure is actually in Django and if you can provide the above information.9 I'm closing this, please reopen if you find the failure is actually in Django and if you can provide the above information.