Don't convert header names to lowercase about httpsnippet HOT 6 CLOSED

I believe there was a reason they were lowered... primarily to avoid duplication, but I have to confirm first ...

from httpsnippet.

+1

from httpsnippet.

As part of discussion in #83 we will move this forward by not lowercasing headers, not de-duping, and making the code not depend on a lowercases content-type key. Stay tuned for a PR...!

from httpsnippet.

Added a branch with a failing test so we can address this once we get a successful test suite and have more confidence in refactors like this: https://github.com/Kong/httpsnippet/tree/fix/74-dont-lowercase-header-keys

from httpsnippet.

This should depend on the HTTP version being used. HTTP/1.1 says header names are case-insensitive while HTTP/2 requires them to be lowercase.

from httpsnippet.

@darrenjennings when do you expect this (part of #83) to be fixed?

from httpsnippet.