This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author tzickel
Recipients pje, rschoon, tzickel
Date 2016-02-19.18:58:06
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1455908286.72.0.148009836972.issue21878@psf.upfronthosting.co.za>
In-reply-to
Content
Just encountered this issue as well.

It's not related to newlines, but to not supporting HTTP or persistent connections (the wsgi.input is the socket's I/O directly, and if the client serves a persistent connection, then the .read() will block forever).

A simple solution is to use a saner wsgi server (gevent works nicely).
Here is their implmentation of the socket I/O wrapper class (Input), and it's read/readlines functions:
https://github.com/gevent/gevent/blob/a65501a1270c1763e9de336a9c3cf52081223ff6/gevent/pywsgi.py#L303
History
Date User Action Args
2016-02-19 18:58:06tzickelsetrecipients: + tzickel, pje, rschoon
2016-02-19 18:58:06tzickelsetmessageid: <1455908286.72.0.148009836972.issue21878@psf.upfronthosting.co.za>
2016-02-19 18:58:06tzickellinkissue21878 messages
2016-02-19 18:58:06tzickelcreate