Message183233
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. |
|
Date |
User |
Action |
Args |
2013-02-28 21:13:47 | karlcow | set | recipients:
+ karlcow, terry.reedy, orsenthil, eric.araujo, r.david.murray, santoso.wijaya, sleepycal, Cal.Leeming, demian.brecht |
2013-02-28 21:13:47 | karlcow | set | messageid: <1362086027.81.0.0280030178207.issue12455@psf.upfronthosting.co.za> |
2013-02-28 21:13:47 | karlcow | link | issue12455 messages |
2013-02-28 21:13:47 | karlcow | create | |
|