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 Carl.Nobile, IcicleSpider, cdwave, edevil, jjlee, martin.panter, nikratio, nnorwitz, orsenthil, rharris, terry.reedy
Date 2016-04-03.12:04:18
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
Thankyou, I think I understand your situation better now (though I don’t understand why Apache doesn’t renegotiate while the request body is being sent).

I would still argue that this is a new feature to be added rather than a bug though, and should only go into Python 3.6+. The original HTTP 1.1 specification (RFC 2068) did not even mention an “Expect: 100-continue” header field, although it does mention the “100 Continue” response. And any change will probably need new APIs and documentation.

Rather than parsing the headers for “100-continue”, I wonder if it would be cleaner adding an API flag to add the header. Or perhaps a new method that explicitly waits for the 100 response.
Date User Action Args
2016-04-03 12:04:18martin.pantersetrecipients: + martin.panter, nnorwitz, terry.reedy, jjlee, orsenthil, cdwave, rharris, edevil, nikratio, Carl.Nobile, IcicleSpider
2016-04-03 12:04:18martin.pantersetmessageid: <>
2016-04-03 12:04:18martin.panterlinkissue1346874 messages
2016-04-03 12:04:18martin.pantercreate