id,summary,reporter,owner,description,type,status,component,version,severity,resolution,keywords,cc,stage,has_patch,needs_docs,needs_tests,needs_better_patch,easy,ui_ux
18807,Inconsistency in the default views,aaugustin,nobody,"`django.views.defaults.permission_denied` will respond ``

403 Forbidden

`` if no ``403.html`` template is found. This behavior was introduced to provide [https://code.djangoproject.com/ticket/5515#comment:16 backwards compatibility]. Generally speaking, it is a reasonable fallback.
I believe that `page_not_found` and `server_error` could benefit from a similar fallback.
That would prevent 404s from turning into 500s when there's no 404.html template. I know we want to encourage custom error pages, but in case a developer skips them, a bare ``

404 Not Found

`` is less damaging than a 500 with a backtrace or no content at all.",Cleanup/optimization,closed,Core (Other),master,Normal,fixed,,,Ready for checkin,1,0,0,0,0,0