#35281: Use HTTP 413 status code for RequestDataTooBig
-----------------------------------------+------------------------
               Reporter:  zvyn           |          Owner:  nobody
                   Type:  Uncategorized  |         Status:  new
              Component:  HTTP handling  |        Version:  5.0
               Severity:  Normal         |       Keywords:
           Triage Stage:  Unreviewed     |      Has patch:  0
    Needs documentation:  0              |    Needs tests:  0
Patch needs improvement:  0              |  Easy pickings:  1
                  UI/UX:  0              |
-----------------------------------------+------------------------
 Other HTTP servers (e.g. Apache, Nginx) report a body which is to large
 with the status code 413 "Payload Too Large".

 I propose to do the same in Django when handling a RequestDataTooBig
 exception in
 
https://github.com/django/django/blob/f931cbec21cce3e2e68239c77614e6aa5026b882/django/core/handlers/exception.py#L63

 This makes the behavior of a typical stack consisting of a reverse proxy
 and a Django project predictable for this type of error.

 I can work on a patch if this change is acceptable to you.
-- 
Ticket URL: <https://code.djangoproject.com/ticket/35281>
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/0107018e192fdff9-2e43b1cf-3619-4b09-84b4-4cc012095da8-000000%40eu-central-1.amazonses.com.

Reply via email to