Capitalization in Custom HTTP Headers #85

Activity

1. ghost assigned

   stamparm

   on Jul 12, 2012
2. stamparm commented on Jul 13, 2012

   

   stamparm

   on Jul 13, 2012

   Member

   More actions

   From RFC 2616, "Hypertext Transfer Protocol -- HTTP/1.1", §4.2, "Message Headers":

   "Each header field consists of a name followed by a colon (":") and the field value. Field names are case-insensitive."
   

   Python does the capitalization as per given RFC standard. Maybe something else is wrong in your case.
3. stamparm

   closed this as completedon Jul 13, 2012
4. ghost assigned

   stamparm

   on Jul 17, 2013
5. hagronnestad commented on Nov 19, 2013

   

   hagronnestad

   on Nov 19, 2013

   More actions

   I have this problem as well. RFC 2616 is nice and all, if every web application would follow it, but that's not the case. I would definitely prefer that the header case would be preserved the way I enter it.

   In my case AuthenticationToken becomes Authenticationtoken which the API won't accept.
6. stamparm commented on Nov 24, 2013

   

   stamparm

   on Nov 24, 2013

   Member

   More actions

   Problem is that Python does the "capitalization" part. We'll need to make a dirty hack to bypass it

   p.s.

   http://bugs.python.org/issue2275
   https://groups.google.com/forum/#!topic/comp.lang.python/Ndl6s0EldKk
7. stamparm

   reopened this on Dec 13, 2013
8. stamparm

   added a commit that references this issue on Jan 2, 2014

   Fix for an Issue #85

   5437f8b
9. stamparm

   closed this as completedon Jan 2, 2014