It appears that once a certain size is exceeded, the request body is not
received at all or truncated to 0.
Here's a minimal view that echos the request body:
def echo(request):
return HttpResponse(request.body)
Then I'm sending files like this:
curl -v -X PUT --data-binary @file -H "Transfer-Encoding: chunked"
http://localhost:8000/echo/
The runserver output will display 0 bytes sent if I try to send a too big
file:
[01/Jul/2015 23:15:05]"PUT /echo/ HTTP/1.1" 200 0
On Wed, Jul 1, 2015 at 2:10 PM, Avraham Serour <tovm...@gmail.com> wrote:
What do you mean by trouble, be more specific
>
> On Wed, Jul 1, 2015, 11:06 PM Justin Karneges <jus...@fanout.io> wrote:
>
>> Hi folks,
>>
>> I'm running into trouble doing a PUT with chunked encoded request body
>> when the size exceeds around 35K. This is with runserver, so there's no
>> Apache or wsgi or anything here.
>>
>> Are there any request body size limits in Django or specifically in
>> runserver? Trying to isolate whether this issue is on the sender side or
>> Django side.
>>
>> Thanks,
>> Justin
>>
>>
--
You received this message because you are subscribed to the Google Groups
"Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to django-users+unsubscr...@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
Visit this group at http://groups.google.com/group/django-users.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-users/CAKFnGOQfvE3aWZ_KCDHh8HVZ4tnzp3zjXeMjaRTzjLWNRu4bHA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
