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 WildCard65, berker.peksag, martin.panter, paul.moore, steve.dower, terry.reedy, tim.golden, vstinner, zach.ware
Date 2018-09-28.10:34:46
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1538130886.53.0.545547206417.issue25095@psf.upfronthosting.co.za>
In-reply-to
Content
Hi William, when I mentioned “Content-Length”, I meant adding it to the response from the server. See the second version of “do_GET” in my earlier comment <https://bugs.python.org/issue25095#msg309522>. But that is no good without also adding the “self.con.close()” line to the client I mentioned in two of my other comments.

In your latest rev. e6b09d4 (and earlier rev. 2022b6f) you send “Content-Length: 0” in a GET _request_, which doesn’t make much sense. GET requests never have bodies of any length. It is the “200 OK” _response_ that should have a body according to HTTP. The server has to shut down the connection or add “Content-Length: 0” (or use chunked encoding) to indicate the end of the body to the proxy.

So I would prefer to either adjust the “do_GET” server function as well as adding “self.con.close()” to the client, or just go back to rev. c1afa6b (“Connection: close”).
History
Date User Action Args
2018-09-28 10:34:46martin.pantersetrecipients: + martin.panter, terry.reedy, paul.moore, vstinner, tim.golden, berker.peksag, zach.ware, steve.dower, WildCard65
2018-09-28 10:34:46martin.pantersetmessageid: <1538130886.53.0.545547206417.issue25095@psf.upfronthosting.co.za>
2018-09-28 10:34:46martin.panterlinkissue25095 messages
2018-09-28 10:34:46martin.pantercreate