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 IcicleSpider
Recipients Carl.Nobile, IcicleSpider, cdwave, edevil, jjlee, martin.panter, nikratio, nnorwitz, orsenthil, rharris, terry.reedy
Date 2016-04-03.20:54:34
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1459716875.05.0.427261727725.issue1346874@psf.upfronthosting.co.za>
In-reply-to
Content
"(though I don’t understand why Apache doesn’t renegotiate while the request body is being sent)"

Apache does attempt to do this, but HttpsConnection is immediately sending the body of the request as fast as the socket will allow, which fills up the SSLRenegBuffer before the renegotiation can occur.

"Or perhaps a new method that explicitly waits for the 100 response."

That is likely a good idea. My httplib.py fork did change the behavior of the endheaders method to return a response object if there was an error returned in response to the "Expect: 100-continue".
History
Date User Action Args
2016-04-03 20:54:35IcicleSpidersetrecipients: + IcicleSpider, nnorwitz, terry.reedy, jjlee, orsenthil, cdwave, rharris, edevil, nikratio, Carl.Nobile, martin.panter
2016-04-03 20:54:35IcicleSpidersetmessageid: <1459716875.05.0.427261727725.issue1346874@psf.upfronthosting.co.za>
2016-04-03 20:54:35IcicleSpiderlinkissue1346874 messages
2016-04-03 20:54:34IcicleSpidercreate