On Fri, Nov 20, 2015 at 5:04 PM, Jim Jagielski <[email protected]> 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.
