Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Lambda invocation fails if no InvocationType specified; should assume default RequestResponse #934

Closed
francisu opened this issue Mar 23, 2020 · 2 comments
Closed

Lambda invocation fails if no InvocationType specified; should assume default RequestResponse #934

francisu opened this issue Mar 23, 2020 · 2 comments

Comments

@francisu
Copy link
Contributor

Bug Report

Current Behavior

Lambda function (to the lambda handler) invoked with no InvocationType fails with a message that 'null' invocation type is not supported.

Expected behavior/code

Per the AWS documentation, if there is no InvocationType, RequestResponse is assumed. In AWS this is handled at the server when the X-Amz-Invocation-Type header is missing.

https://docs.aws.amazon.com/lambda/latest/dg/API_Invoke.html

Environment

  • serverless version: 1.67.0
  • serverless-offline version: 6.0.0
  • node.js version: v10.19.0
  • OS: macOS: 10.14.6

Possible Solution

See forthcoming PR
@francisu
Copy link
Contributor Author

PR: #935

@francisu
Copy link
Contributor Author

Fixed in 6.1.0 with the above PR.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@francisu