Message262827
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:18 | martin.panter | set | recipients:
+ martin.panter, nnorwitz, terry.reedy, jjlee, orsenthil, cdwave, rharris, edevil, nikratio, Carl.Nobile, IcicleSpider |
2016-04-03 12:04:18 | martin.panter | set | messageid: <1459685058.47.0.00808146089104.issue1346874@psf.upfronthosting.co.za> |
2016-04-03 12:04:18 | martin.panter | link | issue1346874 messages |
2016-04-03 12:04:18 | martin.panter | create | |
|