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

Odd Quirk in API Gateway Cache Cluster Use #281

Open
NathanLawrence opened this issue Aug 24, 2016 · 3 comments
Open

Odd Quirk in API Gateway Cache Cluster Use #281

NathanLawrence opened this issue Aug 24, 2016 · 3 comments

Comments

@NathanLawrence
Copy link

While working on #183, I seem to have noticed another odd behavior in API Gateway caching. Perhaps this is my own mistake with the WSGI configuration or I need to be customizing some Swagger JSON to make this happen correctly (as suggested in #116), but API Gateway seems to be over-caching and ignoring additional parameters.

For example, a hit to a flask-RESTful endpoint at [base staged URI]/items/1224 is returning the items listing you would expect if you asked for [base staged URI]/items.

Thoughts?

@Miserlou
Copy link
Owner

I haven't used cache cluster myself, what does [base staged URI]/items/1224/ (with a trailing slash) return?

@NathanLawrence
Copy link
Author

Same problem there, sadly...

@Miserlou
Copy link
Owner

Anything ever come of this one? I still haven't used CC myself.

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

No branches or pull requests

2 participants