This repository has been archived by the owner on Aug 27, 2021. It is now read-only.
fix(handler) ensure multivalueheaders are handled #59
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
gszr
force-pushed
the
fix/handle-multi-value-headers
branch
2 times, most recently
from
048a37f to
b76d430
Compare
Tieske
approved these changes
Jun 14, 2021
|
@gszr updated the docker login, saw you copied it from the docker repo, but that one was bad. See also: Kong/docker-kong#475 This should fix it. |
|
Thank you @Tieske! |
|
Seems this is failing completely now @Tieske. Any ideas? |
|
because I'm an idiot |
Ensure the `multiValueHeaders` field is handled in AWS Lambda proxy integration responses. Fix #53.
Tieske
force-pushed
the
fix/handle-multi-value-headers
branch
from
edc36a5 to
eae7751
Compare
|
Thanks for the help, @Tieske! 👍 |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Ensure the
multiValueHeadersfield is handled in AWS Lambda proxyintegration responses.
Fix #53.