You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The Chalice request object does not expose the original path. I assume this is because the route decorator has already parsed the path in to variables and therefore, you no longer the original. However, there are occasions you might need it. In my case I need to validate a oauth1 signature using the pyLTI module. So this is not really an issue but a feature request.
There is a workaround to the limitation above. API Gateway includes the path in the requestContext which is available from the Chalice request object. Unfortunately, Chalice local mode omits the path (and other keys) from the requestContext. This is a bug as local mode should behave the same way as API Gateway whenever possible. As a result my test cases are failing. Will submit a pull request to fix this.
The text was updated successfully, but these errors were encountered:
This is a two part issue.
The Chalice request object does not expose the original path. I assume this is because the route decorator has already parsed the path in to variables and therefore, you no longer the original. However, there are occasions you might need it. In my case I need to validate a oauth1 signature using the pyLTI module. So this is not really an issue but a feature request.
There is a workaround to the limitation above. API Gateway includes the path in the requestContext which is available from the Chalice request object. Unfortunately, Chalice local mode omits the path (and other keys) from the requestContext. This is a bug as local mode should behave the same way as API Gateway whenever possible. As a result my test cases are failing. Will submit a pull request to fix this.
The text was updated successfully, but these errors were encountered: