By the way, this is also in my big ContentFetcher refactoring patch. Unfortunately I got side tracked halfway through making those changes, and now it's woefully out of sync with HEAD. I can start applying these changes again this week though, since I've got a lot of free time other than I/O.
On Sun, May 25, 2008 at 5:35 PM, Kevin Brown <[EMAIL PROTECTED]> wrote: > The current header handling is a bit wonky anyway, because it's entirely > too verbose for the exceptional case (multiply defined headers). > > A simple solution for the case sensitivity would be to use a TreeMap > instead of a HashMap and pass String.CASE_INSENSITIVE_ORDER as the > comparator. > > > On Sun, May 25, 2008 at 5:23 PM, Brian Eaton <[EMAIL PROTECTED]> wrote: > >> It doesn't look like HttpResponse treats HTTP headers as >> case-insensitive. Any objections to adding toLower() calls in the >> appropriate places to make that happen? >> > >
