#34063: request.POST not populated for multipart/form-data via AsyncClient
-------------------------------------+-------------------------------------
Reporter: Timo Ludwig | Owner: Scott
| Halgrim
Type: Bug | Status: closed
Component: Testing framework | Version: 4.0
Severity: Normal | Resolution: fixed
Keywords: | Triage Stage: Ready for
| checkin
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Carlton Gibson):
Hi Florian.
I did think about it but it doesn't really apply in the ASGI case... For
WSGI we use LimitedStream to stop requests reading beyond their limits,
but each request under ASGI has its own body file — reading beyond that's
not something that can occur.
The error here is an artefact of the testing setup, which sets a
`FakePayload`, which fails loudly for an out of bounds read (rather than
just giving you want it's got) for reasons of its own (which stem from the
dawn of time). (The first pass at DjangoCon was ''"Why doesn't
`FakePayload` behave better?"', but there are tests depending on it doing
what it's doing...)
--
Ticket URL: <https://code.djangoproject.com/ticket/34063#comment:10>
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/01070185675e640f-4d80cc59-df1d-4ef4-a7fd-a42503cd568d-000000%40eu-central-1.amazonses.com.
