id,summary,reporter,owner,description,type,status,component,version,severity,resolution,keywords,cc,stage,has_patch,needs_docs,needs_tests,needs_better_patch,easy,ui_ux 2970,[patch] HttpResponse should treat headers case-insensitively,Adrian Holovaty,Philippe Raoult,"''(Submitted by Bryan O'Sullivan, who had problems with Trac's spam filter.)'' The HttpResponse implementation uses a normal Python dict to store headers. This makes it necessary to have every component that sets headers in a response agree on the exact case to use for every header name. I found this problem while trying to glue a WSGI app into a Django app, only to discover that one believes that a header should be named ""content-type"", while the other prefers ""Content-Type"". This results in a HTTP response that contains both headers, leading to undefined (and currently bad) results on the client side. Probably the HttpResponse class should use a dict-like object that preserves, but ignores, case, so that ""Foo"" and ""fOo"" will map to the same item.",defect,closed,HTTP handling,,normal,fixed,sprintsept14,,Design decision needed,1,0,0,0,0,0