➜

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 Lukasa
Recipients Arfrever, Lukasa, martin.panter, orsenthil, pitrou, rhettinger
Date 2016-09-09.22:24:14
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1473459854.22.0.478328975031.issue22450@psf.upfronthosting.co.za>
In-reply-to
Content 
So, leaping in on the Requests side of things for a moment, two notes. Firstly: copying curl is rarely a bad thing to do, especially for a behaviour curl has had for a long time.

However, in this case the stronger argument is that just because the RFCs say that Accept: */* is implied doesn't mean it can safely be omitted. In practice, origin servers behave unexpectedly when the header is omitted, and in general behave more predictable when it is emitted. For that reason, it should be added by Python's standard library. 

HTTP/1.1 is a protocol where "as deployed" means much more than "as specified", sadly.
History
Date User Action Args
2016-09-09 22:24:14Lukasasetrecipients: + Lukasa, rhettinger, orsenthil, pitrou, Arfrever, martin.panter
2016-09-09 22:24:14Lukasasetmessageid: <1473459854.22.0.478328975031.issue22450@psf.upfronthosting.co.za>
2016-09-09 22:24:14Lukasalinkissue22450 messages
2016-09-09 22:24:14Lukasacreate