#29571: Error 500 when accessing static files that do not exist
-------------------------------------+-------------------------------------
Reporter: dmitriybch | Owner: nobody
Type: Bug | Status: closed
Component: contrib.staticfiles | Version: 2.0
Severity: Normal | Resolution: needsinfo
Keywords: | Triage Stage:
| Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Ramiro Morales):
* status: new => closed
* resolution: => needsinfo
Comment:
In production, the one serving your static files should be your web server
not Django, and so the web server shoudl be in business of reporting 404
or other error.s
That, or there is some missing in your description of your setup.
Generally speaking and following best practices, no Python code should be
running as part of the request cycle for static assets.
Do you get any more details (full tracceback, 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
I'm closing , please reopen if you find the failure is actually in Django
and if you can provide the above information.
--
Ticket URL: <https://code.djangoproject.com/ticket/29571#comment:1>
Django <https://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 unsubscribe from this group and stop receiving emails from it, send an email
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/068.46dbd914a23b2078afa7126822ac0ea5%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
