8000 feat(options): allow to control headers casing by naorpeled · Pull Request #246 · jeremydaly/lambda-api · GitHub
[go: up one dir, main page]

Skip to content

feat(options): allow to control headers casing #246

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Draft
wants to merge 22 commits into
base: main
Choose a base branch
from
Prev Previous commit
oops
  • Loading branch information
naorpeled committed Sep 3, 2023
commit f38ee1b573f5caf272c2deab77fa30e306665bb2
4 changes: 2 additions & 2 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -165,13 +165,13 @@ const api = require('lambda-api')({ version: 'v1.0', base: 'v1' });

For detailed release notes see [Releases](https://github.com/jeremydaly/lambda-api/releases).

# v.1.0.3: allow to control header keys behavior
# v1.0.3: allow to control header keys behavior

In the past, by default, we normalized all headers to be lowercased based on [the http/2 spec](https://www.rfc-editor.org/rfc/rfc9113#name-http-fields).
This has caused issues for some of our consumers, therefore we're adding a new API option called `lowercaseHeaderKeys`.
By default it's set to true, in order to not break the already existing implementation.

# v.1.0: move to AWS-SDK v3
# v1.0: move to AWS-SDK v3

Lambda API is now using AWS SDK v3. In case you're still using AWS SDK v2, please use a lambda-api version that is lower than 1.0.

Expand Down
0