404 page does not display stack trace when Resolver404 is raised from a view
|Reported by:||Grzegorz Nosek||Owned by:||Grzegorz Nosek|
|Has patch:||no||Needs documentation:||no|
|Needs tests:||no||Patch needs improvement:||no|
Related to #18373, the 404 error page served when django.core.urlresolvers.resolve() fails does not contain the exception stack trace, which makes finding the failing call unnecessarily difficult.
When the resolve() call fails in a view, the error should actually be 500 (it's not the user's fault), but for backwards compatibility the response code will have to remain 404 (as discussed with Honza Kral last year).
Change History (5)
comment:1 Changed 3 years ago by
|Owner:||changed from nobody to Grzegorz Nosek|
|Status:||new → assigned|