#21668: Invalid upload_to FileField attribute results in hard-to-debug "Bad
Request" 400 error.
-------------------------------------+-------------------------------------
Reporter: GDorn | Owner:
Type: | anubhav9042
Cleanup/optimization | Status: assigned
Component: Documentation | Version: master
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by timo):
This regressed in 1.6 with this commit:
https://github.com/django/django/commit/d228c1192ed59ab0114d9eba82ac99df611652d2
#diff-dbd7d9159676b15fc9a096b0adb919e9R173
I think we should consider returning a `technical_500_response` in the
handling of `SuspiciousOperation` as we did before if `settings.DEBUG is
True` rather than invoking `handler400`.
--
Ticket URL: <https://code.djangoproject.com/ticket/21668#comment:9>
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 [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/063.3eebdcb24355014f3c7ee6508356b833%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
