#29427: RequestDataTooBig raised in request.py prevents Middleware from
returning a
valid response
-------------------------------+------------------------------------
Reporter: S. Paquette | Owner: nobody
Type: Bug | Status: new
Component: HTTP handling | Version: 1.11
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------+------------------------------------
Comment (by Carlton Gibson):
Claude's patch looks fine but doesn't seem to address the underlying
issue. (Why is a response not returned when/if the request doesn't have a
body set.)
I attached a project using the `HandleDataTooBigMiddleware` but failing to
reproduce the issue.
`DEBUG=TRUE`: Expected debug error page.
`DEBUG=False`: Expected JSON response.
As the project is `DEBUG=False`. `./manage.py runserver`, then:
{{{
~ $ curl -X "POST" "http://127.0.0.1:8000/reproduce/"; \
> -H 'Content-Type: application/x-www-form-urlencoded; charset=utf-8'
\
> --data-urlencode "testing=123456789"
{"info": "File too big"}
}}}
(Testing against `master`, pre-3.0 and `stable/1.11.x` — same results.)
It would be nice to pin down the underlying issue here.
--
Ticket URL: <https://code.djangoproject.com/ticket/29427#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/068.e5addc9f4c7b61b2090226de3ee4ddad%40djangoproject.com.
