#17187: Incompatibility with Cherokee webserver's FastCGI handling
-------------------------------------+-------------------------------------
Reporter: sciyoshi | Owner: sam@…
Type: Bug | Status: new
Component: HTTP handling | Version: 1.3
Severity: Normal | Resolution:
Keywords: cherokee flup | Triage Stage:
fastcgi fcgi content-length | Unreviewed
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 1 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Leo):
* cc: leos@… (added)
Comment:
A similar issue happens when running against uWSGI. Django attempts to do
a read() even if the content-length us explicitly set to zero. The result
is that the read() call blocks.
It should properly distinguish between unknown content-length (when trying
to read might make sense) and one explicitly set to zero.
The repro in my case is really simple. Get the latest uWSGI, spin up
simple django app, send a post with nothing in it.
--
Ticket URL: <https://code.djangoproject.com/ticket/17187#comment:6>
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 post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en.
