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 karlcow
Recipients Cal.Leeming, demian.brecht, eric.araujo, karlcow, orsenthil, r.david.murray, santoso.wijaya, sleepycal, terry.reedy
Date 2013-02-28.21:13:47
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1362086027.81.0.0280030178207.issue12455@psf.upfronthosting.co.za>
In-reply-to
Content
Note that HTTP header fields are case-insensitive.
See http://tools.ietf.org/html/draft-ietf-httpbis-p1-messaging#section-3.2

   Each HTTP header field consists of a case-insensitive field name
   followed by a colon (":"), optional whitespace, and the field value.

Basically the author of a request can set them to whatever he/she wants. But we should, IMHO, respect the author intent. It might happen that someone will choose a specific combination of casing to deal with broken servers and/or proxies. So a cycle of set/get/send should not modify at all the headers.
History
Date User Action Args
2013-02-28 21:13:47karlcowsetrecipients: + karlcow, terry.reedy, orsenthil, eric.araujo, r.david.murray, santoso.wijaya, sleepycal, Cal.Leeming, demian.brecht
2013-02-28 21:13:47karlcowsetmessageid: <1362086027.81.0.0280030178207.issue12455@psf.upfronthosting.co.za>
2013-02-28 21:13:47karlcowlinkissue12455 messages
2013-02-28 21:13:47karlcowcreate