-
Notifications
You must be signed in to change notification settings - Fork 421
HTTP API non-$default stage includes stage in rawPath as a prefix #621
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
@michaelbrewer created the issue so we don't forget |
actually I'm wrong here, |
HTTP API v2 does seem to add the stage as part of Need to test with additional stages and once again with $default. {
"routeKey": "ANY /payment/{invoice+}",
"rawPath": "/default/payment/invoiceABC",
"requestContext": {
"domainName": "api.serverlessa.dev",
"http": {
"method": "GET",
"path": "/default/payment/invoiceABC"
},
"routeKey": "ANY /payment/{invoice+}",
"stage": "default"
},
"pathParameters": {
"invoice": "invoiceABC"
}
}
|
Yep, that's another piece we need to work on to strip the stage IF not $default in HTTP API payload, or else it'll fail routing too. Brand new HTTP API using $default stage {
"routeKey": "GET /payment",
"rawPath": "/payment",
"requestContext": {
"domainName": "api.serverlessa.dev",
"http": {
"method": "GET",
"path": "/payment"
},
"routeKey": "GET /payment",
"stage": "$default"
}
} |
@michaelbrewer v2 payload
v1 payload
|
Coming in today's release. |
What were you trying to accomplish?
Configure a resource (/payment) with method in HTTP API to work with Event Handler utility.
Expected Behavior
Route to match
Current Behavior
API Gateway event handler returns 404
Possible Solution
Strip the stage out in the event path if available.
Steps to Reproduce (for bugs)
$default
todefault
Environment
The text was updated successfully, but these errors were encountered: