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 martin.panter
Recipients martin.panter, paul.moore, steve.dower, terry.reedy, tim.golden, vstinner, zach.ware
Date 2015-09-16.12:38:11
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1442407091.89.0.0584776667937.issue25095@psf.upfronthosting.co.za>
In-reply-to
Content
According to those back traces, the server has apparently already handled one request and is waiting for a second request. However the client is still waiting for a response from its original request.

Some things I might try would be to disable the server, and make my own dummy server to see if it responds to that. Similarly, disable the client and manually make a request to the server and see what the response is. On Linux the “socat” or “netcat” programs are useful for this stuff, or you can just use the Python interactive interpreter to create a socket and send and receive.

Client connection is made at <https://hg.python.org/cpython/file/v3.5.0/Lib/test/test_httpservers.py#l252>. Server is constructed at <https://hg.python.org/cpython/file/v3.5.0/Lib/test/test_httpservers.py#l42>.

You could also try adding self.con.set_debuglevel(99) to the test_get() method, though I suspect it will just output the request sent, and not report any reply or headers. In my case the test works, and I see:

send: b'GET / HTTP/1.1\r\nHost: 127.0.0.1:48059\r\nAccept-Encoding: identity\r\n\r\n'
reply: 'HTTP/1.1 200 OK\r\n'
[Unit test output]
header: Server header: Date $
History
Date User Action Args
2015-09-16 12:38:11martin.pantersetrecipients: + martin.panter, terry.reedy, paul.moore, vstinner, tim.golden, zach.ware, steve.dower
2015-09-16 12:38:11martin.pantersetmessageid: <1442407091.89.0.0584776667937.issue25095@psf.upfronthosting.co.za>
2015-09-16 12:38:11martin.panterlinkissue25095 messages
2015-09-16 12:38:11martin.pantercreate