How do I find my HTTP cache?

# View cache data

1. Click the Application tab to open the Application panel.
2. Expand the Cache Storage section to view available caches.
3. Click a cache to view its contents.
4. Click a resource to view its HTTP headers in the section below the table.
5. Click Preview to view a resource’s content.

What is the cache key?

A cache key is an index entry that uniquely identifies an object in a cache. You can customize cache keys by specifying whether to use a query string (or portions of it) in an incoming request to differentiate objects in a cache.

What is HTTP cache-control?

Cache-control is an HTTP header used to specify browser caching policies in both client requests and server responses. Policies include how a resource is cached, where it’s cached and its maximum age before expiring (i.e., time to live).

Is the HTTP headers included in the cache key?

The HTTP headers in viewer requests that CloudFront includes in the cache key and in origin requests. For headers, you can choose one of the following settings: None – The HTTP headers in viewer requests are not included in the cache key and are not automatically included in origin requests.

What are the values in the cache key?

Cache key settings specify the values in viewer requests that CloudFront includes in the cache key. The values can include URL query strings, HTTP headers, and cookies. The values that you include in the cache key are automatically included in requests that CloudFront sends to the origin, known as origin requests.

How does a proxy cache an HTTP request?

The proxy gets the request, examines it for cache headers, and sends it to the server. Then the proxy examines the response and, if it is cacheable, caches it with the URL as the key (along with some headers in certain cases) and the response as the value.

How does the cache key work in edge?

The cache key is the unique identifier for every object in the cache, and it determines whether a viewer request results in a cache hit. A cache hit occurs when a viewer request generates the same cache key as a prior request, and the object for that cache key is in the edge location’s cache and valid.