Dom Cote added the comment:
Just bumped into this issue today using bobo.
On the first attempt to load a page, it's OK, because there is something to
read. But if you hit the "reload" button on the browser, for some reason, it
will connect with the server a second time after the request is
Bert JW Regeer added the comment:
This is still very much an issue, and makes it more difficult to write generic
python request/response libraries because we can't assume that a read() will
return, and relying on the Content-Length being set is not always possible
unfortunately.
--
tzickel added the comment:
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
Changes by Berker Peksag berker.pek...@gmail.com:
--
nosy: +pje
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue21878
___
___
Python-bugs-list
Robin Schoonover added the comment:
Issue also occurs if .read() is used with no size.
--
title: wsgi.simple_server's wsgi.input readline waits forever for
non-multipart/form-data - wsgi.simple_server's wsgi.input read/readline waits
forever in certain circumstances
