API Gateway Proxy: headers are case sensitive

Description

HTTP headers are case insensitive according to the HTTP spec. However, the only way to access request headers is:

request.Headers["My-header"];

which is case sensitive.

Reproduction Steps

This code below should return the same header value:

var header1 = request.Headers["My-header"];
var header2 = request.Headers["My-hEAder"];
var header3 = request.Headers["my-headEr"];

but it’s returning different values because header name is case sensitive. You can easily check this code by yourself.

Logs

No logs are necessary.

Environment

• Build Version: Amazon.Lambda.Core 2.0.0, Amazon.Lambda.APIGatewayEvents 2.4.0
• OS Info: Windows 10
• Build Environment: VSCode + Terminal dotnet
• Targeted .NET Platform: netcoreapp3.1

Resolution

• 👋 I can/would-like-to implement a fix for this problem myself

---

This is a 🐛 bug-report

[ashishdhingra]

@Mikilll94 Thanks for your response. I just came across Amazon API Gateway important notes. For the bullet point API Gateway enacts the following restrictions and limitations when handling methods with either Lambda integration or HTTP integration, it mentions Header names and query parameters are processed in a case-sensitive way.. Looks like this is a limitation from the service side where user could send 2 headers with same name, but different in case. Given this limitation, I’m not sure how this could be implemented in Lambda HLL. Hope this helps.

[github-actions[bot]]

⚠️COMMENT VISIBILITY WARNING⚠️

Comments on closed issues are hard for our team to see. If you need more assistance, please either tag a team member or open a new issue that references this one. If you wish to keep having a conversation with other community members under this issue feel free to do so.