fix: enable response compression when using multi-value headers#6936
Conversation
|
Thanks a lot for your first contribution! Please check out our contributing guidelines and don't hesitate to ask whatever you need. |
a02c8f6 to
5645985
Compare
|
leandrodamascena
left a comment
There was a problem hiding this comment.
Thanks a lot for this PR @kimsappi! I read your comment in the issue and I agree.
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## develop #6936 +/- ##
===========================================
- Coverage 96.21% 96.20% -0.01%
===========================================
Files 273 273
Lines 12704 12709 +5
Branches 947 949 +2
===========================================
+ Hits 12223 12227 +4
Misses 377 377
- Partials 104 105 +1 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
3448989
into
aws-powertools:develop
|
Awesome work, congrats on your first merged pull request and thank you for helping improve everyone's experience! |



Issue number: #6912
Summary
Changes
Enabled REST response compression to work when multi-value headers are enabled for REST resolvers. Previously only the Lambda invocation event's
"headers"field was considered, now"multiValueHeaders"is used when present, relying on generic Powertools functionality (event.resolved_headers_field).User experience
Previously response compression would not work if the Lambda function integration had multi-value headers enabled. Now it does.
Checklist
If your change doesn't seem to apply, please leave them unchecked.
Is this a breaking change?
RFC issue number:
Checklist:
Acknowledgment
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.
Disclaimer: We value your time and bandwidth. As such, any pull requests created on non-triaged issues might not be successful.