> On Nov 20, 2015, at 11:25 AM, Yann Ylavic <ylavic....@gmail.com> wrote: > > On Fri, Nov 20, 2015 at 5:04 PM, Jim Jagielski <j...@jagunet.com> wrote: >> Ugg... I *just* noticed: >> >> However, header field names MUST be converted to lowercase >> prior to their encoding in HTTP/2. A request or response >> containing uppercase header field names MUST be treated as >> malformed > > Gain some cycles (client side), to the detriment of existing apps... > This won't help H1->H2, at least.
Yeah... This just seemed coincidental considering the other thread about the tokens themselves.
