#32329: CSRF failure incorrectly reported on upload when there is a problem with
storage
------------------------------------+------------------------------------
Reporter: IO | Owner: nobody
Type: Bug | Status: new
Component: CSRF | Version: 3.1
Severity: Normal | Resolution:
Keywords: uploads csrf admin | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
------------------------------------+------------------------------------
Changes (by Tim Graham):
* component: File uploads/storage => CSRF
Comment:
Maybe there's an opportunity to use more specific exception catching than
`OSError` (#20128 added it as `IOError` before it was updated to `OSError`
in 7785e03ba89aafbd949191f126361fb9103cb980). Too bad we don't have the
original exception in #20128 so we can see exactly where that exception
comes from and determine if it's actually `OSError`/`IOError` on Python 3.
--
Ticket URL: <https://code.djangoproject.com/ticket/32329#comment:5>
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 view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/061.ba6d81dc8a5f74cde0d504df40bb8420%40djangoproject.com.
