-
Notifications
You must be signed in to change notification settings - Fork 128
"error": "Method not allowed" #182
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
@jthomerson @jeremydaly help me pls |
Hey @raja-vcomply! Can you post some sample code? |
@raja-vcomply - I just ran into this too. I was using API Gateway V2, but it appears lambda-api won't support the v2.0 event payload format until
Originally posted by @jeremydaly in #174 (comment) If this sounds like your case, you can force the API Gateway V2 to use the v1.0 payload format in the settings. I also noticed the new |
If I understand the situation correctly @codyfyi, I believe it does support v2.0 events. Your code should be this.
|
When i am hitting the route its returning "method not allowed"
The text was updated successfully, but these errors were encountered: