-
Notifications
You must be signed in to change notification settings - Fork 421
Bug: Event handler does not accept null header for compression #1327
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
Comments
Thanks for opening your first issue here! We'll come back to you as soon as we can. |
hey @tbuatois thank you for flagging this and even for taking the time to solve it, much appreciated! Question for you: can this wait until our next release this Friday or is that impacting you now? I suspect it's the former |
Hey @heitorlessa, It can surely wait for the next release ! Thanks for asking. |
This is now released under 1.26.6 version! |
Expected Behaviour
As the documentation stated:
The client must send the Accept-Encoding header, otherwise a normal response will be sent.
When testing my API Gateway integration with lambda from the AWS Console, without specifying header, this send a null header.
Current Behaviour
Throw an error for a request with empty/null headers to a method with
compress=True
:'NoneType' object has no attribute 'items'", "errorType": "AttributeError"
That was due to an error from api_gateway.py at line 212:
Code snippet
Possible Solution
No response
Steps to Reproduce
AWS Lambda Powertools for Python version
latest
AWS Lambda function runtime
3.9
Packaging format used
Lambda Layers
Debugging logs
The text was updated successfully, but these errors were encountered: