- 最新
- 投票最多
- 评论最多
As mentioned in the document https://docs.aws.amazon.com/apigateway/latest/developerguide/api-gateway-caching.html, "When a cached method or integration has parameters, which can take the form of custom headers, URL paths, or query strings, you can use some or all of the parameters to form cache keys. API Gateway can cache the method's responses, depending on the parameter values used." So where you define the cache key will determine at what point will the incoming request be evaluated against the cached keys.
If you have defined a proxy resource only and no other resource in the API, then the settings on the proxy resource will apply on all resources. If there are more specific resources defined, then the settings on those specific resources will apply to those specific resources and the proxy settings will apply to every other resource. To understand how proxy resources work, please take a look at https://docs.aws.amazon.com/apigateway/latest/developerguide/api-gateway-method-settings-method-request.html under this section "Use a proxy resource to streamline API setup".
相关内容
- AWS 官方已更新 1 年前
- AWS 官方已更新 1 年前
- AWS 官方已更新 2 年前
Hi Indranil, thank you. But in both the first 2 screenshots I'm inside the "proxy resource" and at GET method definition, I'm not configuring other resources or other methods, so I still have doubts ;) About the necessity to mark as cacheable the proxy path parameter, do you have any hint?