![]() ![]() To uniquely identify responses in the cache server, the API gateway uses cache keysĭerived from the GET, HEAD, and OPTIONS requests that elicited the responses. Response caching request and response policies that you set up, and ignores anyĬache-control headers (if present) in the request or the response. In the cache server for GET, HEAD, and OPTIONS requests, provided the responses haveĪn HTTP status code of 200, 204, 301, or 410. Responses are already stored in the cache server. Gateway attempts to match a new request with previous similar requests for which Requests from API clients to routes that have response caching policies. When you have enabled an API gateway for response caching, the API gateway analyzes Policies and response policies (see Adding Response Caching Request and Response Policies) set up response caching for individual routes in the API gateway using request.enable response caching on the API gateway (see Enabling Response Caching on an API Gateway).To configure an API gateway for response caching, you: That is similar to the original request, without sending the later request to the Retrieve previously stored data from the cache server in response to a later request.Store data in the cache server that has been returned by a back-end service in.You canĬonfigure API gateways managed by the API Gateway The API Gateway service can integrate with an externalĬache server that you already have access to, such as a Redis or KeyDB server. They can be satisfied by retrieving data from a response cache rather than sending the Requests in case the responses can be re-used later. One way to reduce that load is to cache responses to Typically, you'll want to avoid placing unnecessary load on back-end services to improve
0 Comments
Leave a Reply. |