karl added the comment:
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.
----------
nosy: +karlcow
_______________________________________
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/issue12455>
_______________________________________
_______________________________________________
Python-bugs-list mailing list
Unsubscribe:
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
