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 rhettinger
Recipients Arfrever, martin.panter, orsenthil, pitrou, rhettinger
Date 2015-11-01.07:18:04
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
> What do you think, Raymond

Before dismissing this, we should get a better understanding of why "Accept: */*" is so widely used in practice.

Here's what we know so far:
* The header made a difference to the Facebook Graph API.
* Curl (a minimalist) includes "Accept: */*", Host, and User-Agent.
* Firefox includes "*/*" at the end of its list of acceptable types.
* Kenneth Reitz's requests module uses "Accept: */*" by default.
* The poolmanager in urllib3 uses "Accept: */*" by default and has a comment that that and the "Host" header are both needed by proxies.
* I'm also seeing "Accept: */*" in book examples as well.  See and
Date User Action Args
2015-11-01 07:18:04rhettingersetrecipients: + rhettinger, orsenthil, pitrou, Arfrever, martin.panter
2015-11-01 07:18:04rhettingersetmessageid: <>
2015-11-01 07:18:04rhettingerlinkissue22450 messages
2015-11-01 07:18:04rhettingercreate