#35281: Use HTTP 413 status code for RequestDataTooBig
--------------------------------------+------------------------------------
     Reporter:  Milan Oberkirch       |                    Owner:  (none)
         Type:  Cleanup/optimization  |                   Status:  new
    Component:  HTTP handling         |                  Version:  5.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 Natalia Bidart):

 Replying to [comment:9 Ahmed Ibrahim]:
 > Replying to [comment:8 Simon Charette]:
 > > Robin feel free to assign but take a minute to digest
 [https://github.com/django/django/pull/17960#discussion_r1518576372 why
 the efforts have stalled in the past weeks] first. I don't this this
 constitutes an ''easy picking'' anymore.
 > >
 > > Milan, I'll unassign given you closed your MR. Thank you for kicking
 off the work.
 >
 > Can I handle this one? I have the time needed

 Hello Ahmed, thank you for your interest in helping Django. Yes, you can
 assign yourself the ticket and work on it. Please take into consideration
 all the commentary, specifically the one from the closed PR.
-- 
Ticket URL: <https://code.djangoproject.com/ticket/35281#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/0107019123665098-4f03066b-e918-4530-a498-8dadb141e37d-000000%40eu-central-1.amazonses.com.

Reply via email to