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 Arfrever, martin.panter, orsenthil, pitrou, rhettinger
Date 2015-11-01.09:30:43
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
According to all the HTTP 1.1 RFCs, having */* at the end means you accept any other content type if none of the higher priority ones are available (otherwise you risk a 406 Not Acceptable error). So that explains why Firefox has */* tacked on.

Requests copied from Curl: <>. Similarly, it is in urllib3 “because that’s what cURL had by default”. Brief discussion at <>, where they decided to leave things as they already were.

So all roads seem to lead to Curl. Curl’s “initial revision” (Dec 1999) had “Accept: image/gif, image/x-xbitmap, image/jpeg, image/pjpeg, */*”, which was changed to “Accept: */*” in <> in 2004. I don’t see any reasons given. I just left a question on Git Hub about this, so maybe we might get some sort of answer.

Wget also includes “Accept: */*”. But it gives no explanations either, and it was present right from the “initial revision” also in Dec 1999 (presumably Source Forge started about then).
Date User Action Args
2015-11-01 09:30:43martin.pantersetrecipients: + martin.panter, rhettinger, orsenthil, pitrou, Arfrever
2015-11-01 09:30:43martin.pantersetmessageid: <>
2015-11-01 09:30:43martin.panterlinkissue22450 messages
2015-11-01 09:30:43martin.pantercreate