➜

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 Lukasa, SilentGhost, martin.panter
Date 2016-10-31.23:57:08
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1477958228.8.0.138807373976.issue28570@psf.upfronthosting.co.za>
In-reply-to
Content 
Consuming and ignoring 1xx responses seems reasonable for general cases. Treating 101 (Switching Protocols) as a special case also seems reasonable.

I also agree it would be good to provide an API to return these responses (at least after the request is completely sent). Perhaps a new flag, c.getresponse(informational=True), or a new method, c.get_informational_response(timeout=...). The timeout is for servers that do not support “Expect: 100-continue” mode; see Issue 1346874.

There is also Issue 25919 discussing how to handle responses (including 1xx) while concurrently sending the request. That is a harder problem, but may be solvable with a few new APIs.
History
Date User Action Args
2016-10-31 23:57:08martin.pantersetrecipients: + martin.panter, SilentGhost, Lukasa
2016-10-31 23:57:08martin.pantersetmessageid: <1477958228.8.0.138807373976.issue28570@psf.upfronthosting.co.za>
2016-10-31 23:57:08martin.panterlinkissue28570 messages
2016-10-31 23:57:08martin.pantercreate