-
Notifications
You must be signed in to change notification settings - Fork 35
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
Question on caching with querystring #71
Comments
Hi @stoverlee,
If you have settings like:
Then it will create a cache entry for all the different values it may receive of
You're right that the README needs to be updated. I need to add some of what's here - and also that In your example, your parameters would be part of the
Multi-value query strings would look something like:
I can only think of a way to have a catch-all for paths:
This would allow you to cache any paths to the right of
In lambda code, you would have access to the path variable through the However, this doesn't seem to work for query string parameters, so for the paths:
the same cache entry would be created. Please let me know if it doesn't make sense. Edit: I just noticed this PR on Later edit: The PR was good, but didn't add support for |
@DianaIonita Hello, I imagine there is some kind of an endpoint like |
Hi @pavlelekic, Yes, you can invalidate specific cache keys by setting the header You might also need to configure per-key cache invalidation authorization with these plugin settings: custom:
apiGatewayCaching:
enabled: true
perKeyInvalidation:
requireAuthorization: true # default is true
handleUnauthorizedRequests: Fail # default is "IgnoreWithWarning". |
Thanks @DianaIonita! |
Hi @pavlelekic, You can do that, for example, via the API Gateway console, in the Stage editor: |
Thanks! |
How to cache full query string? |
Hi @vvmspace,
Please consider raising another issue if you'd like to have further discussions around this topic. |
Hi, I have a couple of questions on how caching works with querystrings, and perhaps the README.md can be updated to clarify this:
Suppose we're working with the following endpoint
/test
and it can take 2 optional querystring parameters:param1
andparam2
/test
?/test?param1=test
,/test?param2=test
,/test?param1=test¶m2=test
?Thanks
The text was updated successfully, but these errors were encountered: