#34063: request.POST not populated for multipart/form-data via AsyncClient
-------------------------------------+-------------------------------------
     Reporter:  Timo Ludwig          |                    Owner:  Kevan
                                     |  Swanberg
         Type:  Bug                  |                   Status:  assigned
    Component:  Testing framework    |                  Version:  4.0
     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 Scott Halgrim):

 I've been researching this ticket for a few hours at DjangoCon with
 Carlton. He suggested (and I agree), that now would be a good time to
 summarize what we've learned. This is not a full understanding of the
 issue, but merely a status report, so to speak.

 We've found we're able to reduce the surface area, so to speak, by adding
 this smaller test to `test_fakepayload.py`, which also errors out in the
 same way

 {{{#!python
 def test_read_small_file(self):
     payload = FakePayload(b'--BoUnDaRyStRiNg\r\nContent-Disposition: form-
 data; name="value"\r\n\r\n37\r\n--BoUnDaRyStRiNg--\r\n')
     payload.read(65536)
 }}}

 This is basically what's happening in the example test `test_post`
 provided above. The `FakePayload` object has its `read` method called by
 `ChunkIter` in `MultiPartParser` with a value of 65_536.

 So maybe the question now is, should `FakePayload` handle this in a
 different way, or `MultiPartParser` and `ChunkIter` not be sending in a
 number larger than the length of the body?

-- 
Ticket URL: <https://code.djangoproject.com/ticket/34063#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 django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/01070183f75d629c-52d07cc8-7985-4254-b4b0-509d2d3f2636-000000%40eu-central-1.amazonses.com.

Reply via email to