#30015: HTTP server doesn't clear previous request data in keep-alive
connection.
-------------------------------------+-------------------------------------
Reporter: Konstantin Alekseev | Owner: nobody
Type: Bug | Status: closed
Component: HTTP handling | Version: 2.1
Severity: Release blocker | Resolution: fixed
Keywords: keep-alive, server | Triage Stage: Ready for
| checkin
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Tim Graham <timograham@…>):
In [changeset:"08f78a4fc8e7882f9fcad19aa6d497f749a9d261" 08f78a4f]:
{{{
#!CommitTicketReference repository=""
revision="08f78a4fc8e7882f9fcad19aa6d497f749a9d261"
[2.1.x] Fixed #30015 -- Ensured request body is properly consumed for
keep-alive connections.
Backport of b514dc14f4e1c364341f5931b354e83ef15ee12d and
bbe28fa07658f00786dc1d91ee281b4daac22d07 from master.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/30015#comment:7>
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 post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/067.862d0675023e78764da8c9c914adfbbf%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
