[BUG] Headers are shown in all lowercase even if they were not

Describe the bug If I send a request to the request bin with an upper or mixed case header it shows up in the interface as all lowercase.

To Reproduce Steps to reproduce the behavior:

1. Send a request to your request bin with a header for example curl -H "MIXEDcase: 1" your-bin-url
2. Look at the headers as shown by the request bin UI
3. See that it appears as mixedcase: 1

Expected behavior It should show the headers exactly as they were sent.

Additional context I do recognize that according to the HTTP spec headers are meant to be case-insensitive. But this does not mean that all systems treat them that way. For example, AWS Lambda Proxy Integration provides the headers in a case-sensitive dictionary at event.headers without normalizing their case. Pipedream can therefore lead me astray when I’m inspecting requests.

[dylburger]

Yes, we also operate requestbin.com, but the core of our development work is done on pipedream.com. We don’t operate an issue tracker for RequestBin, but I noted it internally.

[tremby]

I didn’t realize they were two different things – logo on the site I was using says Pipedream. I only heard of it via a link in these docs. (This is the first 3rd-party service, not the one I’m adding support for.)

I’ll believe you that the bug doesn’t exist in the software you thought I was using. Sorry for posting in the wrong place. It sounds like the two pieces of software are related though – is there an issue tracker for requestbin.com? I couldn’t see any contact information or links to support or feedback or a repo at all on that site.