-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Dynamic routes not working? #48
Comments
That code doesn't work locally either. You need to add to the route string. |
My bad, pasted the wrong code. This works locally:
But not when deployed |
Going to sleep now, will check in the morning. Thanks for reporting. |
Maybe it doesn't work in Asia Pacific region yet? Try US East? https://oo8j6uj6i1.execute-api.us-east-1.amazonaws.com/dev4/client/VVV |
I just had the same issue when creating a brand new lambda (not zappa) endpoint with an api gateway in us-west-2 -- could just be slow setup of the api gateway part (it does warn about a potential 15 minute setup time). |
zappa works fine, this was a PEBKAC problem: for some reason I had set the 'parameter_depth' parameter to 1 |
Ah, okay! (I just did that for the demo demo gif to make it go faster!) |
First off, thanks for an amazing project! I've just started trying it out and I've run in to a problem.
This programming works locally:
`import flask
app = flask.Flask(name)
@app.route('/client/', methods=['GET'])
def hello(id):
return 'Hello ' + id
if name == 'main':
app.run()`
But when I deploy I and try with something like
https://107uk4y3sh.execute-api.ap-northeast-1.amazonaws.com/prod4/client/VVV
I get {"message": "Missing Authentication Token"}
Is there anything I need to do in zappa_settings.json to get this work. Changing the code to just have /client as path works fine.
Thanks
The text was updated successfully, but these errors were encountered: