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.

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

methodArn should contain request.path #274

Merged
merged 1 commit into from Jul 26, 2017
Merged

Conversation

mjmac
Copy link
Contributor

@mjmac mjmac commented Jul 24, 2017

When invoking a custom authorizer, supply the requested path
instead of the configured endpointPath. This matches AWS
behavior.

When invoking a custom authorizer, supply the requested path
instead of the configured endpointPath. This matches AWS
behavior.
@dherault dherault merged commit 86d9b1c into dherault:master Jul 26, 2017
@dherault
Copy link
Owner

Thanks @mjmac ! v3.15.2

@sahandseifi
Copy link

sahandseifi commented Jul 9, 2020

Hey there,

Sorry for re-opening this, but I believe the changes in 5ff81fb have brought back this and #273

Essentially, during the authorization process the requested methodArn looks like: /user/{pathParam}. But, API Gateway authorizer behavior suggests that the methodArn look like /user/123

Unfortunately I am not sure how to solve this without bringing back #980, but if anyone has suggestions I can create a PR.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants