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
[BUG] multiValueHeaders not being sent back (ALB) #64
Comments
Looking tonite, expect feedback within next days. Thx and take care!
tor. 30. apr. 2020 16.40 skrev Aaron Macks <notifications@github.com>:
… Assigned #64 <#64>
to @sloev <https://github.com/sloev>.
—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub
<#64 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAGVGUOF3KHRM4KXRPLPP63RPGEUZANCNFSM4MVUAFBA>
.
|
there is not enough for me here to work on, sorry. i would like
If you have time to supply any of that in a pr i will take time to verify and get it in. If not i will not have the time right now to do the journey myself, sorry :-) |
ok, I will put together a PR in the next day or 3 |
Thx
ons. 6. maj 2020 16.22 skrev Aaron Macks <notifications@github.com>:
… ok, I will put together a PR in the next day or 3
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#64 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAGVGUJRGBRK3BMYUKQYNELRQFXBFANCNFSM4MVUAFBA>
.
|
fixed in #65 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
It looks like ALB needs support for
multiValueHeaders
as part of the return JSON for things like Content-Type, headers does not seem to be properly passed through the ALB. I added amultiValueHeader
element by copying and modifyingheaders
in theto_json
andinner_lambda_handler
and it seems to work as expected and the ALB properly interprets. I can submit a PR, but I cannot vouch for the quality of the code, however it does seem to workThe text was updated successfully, but these errors were encountered: