ArvanCloud Cache Response Analysis
The ar-cache response header ensures that THE website's resources are cached in Arvan Cloud's edge servers. This header identifies the caching status. The following article analyzes these different statuses.
What Does Each Caching Status Mean?
Once Arvan Cloud's Content Distribution Network (CDN) service is activated, and the website's resources are cached in Arvan Cloud's edge servers, the ar-cache header will be added to make it possible for users tracking the caching status of them.
To check the response headers, do as below:
- Go to: Chrome > Setting
- Click on: More Tools > Developer Tools
- Use Ctrl+Shift+I
The cache status in this header can be one of the following options:
HIT: The HIT status means the requested resource is cached in Arvan Cloud's edge server, and it will have a specific response.
MISS: The MISS status indicates that the requested resource does not exist in Arvan Cloud's edge server, and the response is received from the origin server.
EXPIRED: The EXPIRED status signifies that the requested resource exists in Arvan Cloud's edge server, and since it is expired, the origin server has already responded to it.
STALE: The STALE status happens rarely, and it means that Arvan Cloud's edge server sent a stale and expired resource as a response. This happens because the Arvan Cloud server is validating the origin server's resource simultaneously based on a user requested.
IGNORED: The IGNORED status indicates that the requested resource cannot be cached, but since the requests did not reach its limits (Maximum three), the origin server already responded. Once it passes the allowed numbers, the status will change to HIT.
REVALIDATED: The REVALIDATED status signifies that Arvan Cloud's edges server used the stale version of the cached resource. The difference is the edge server used If-Modified-Since or If-None-Match headers of the origin servers to validate the resource.
UPDATING: The UPDATING status means that the requested resource is updating on Arvan Cloud's edge server, and the received response is the cached stale version that existed in the server.
Why Doesn't ar-cache Response Header Exist?
If there is no ar-cache sign among the other Arvan Cloud's headers, it implies that the intended resource is considered the website's external resources.
Check out the articles below to learn about all the cached suffixes in Arvan Cloud's edge servers and the general caching settings in Arvan Cloud User Panel.
- The Default Cacheable Suffixes in Arvan Cloud CDN
- What is Caching and How to Adjust Its Setting in the Arvan Cloud Panel?
Please note that if the Cache-Control headers are added to the website's resources based on no-cache and private commands, Arvan Cloud's edge server cannot cache these resources. Therefore, if you want these resources to be cached in Arvan Cloud's edge servers, adjust the correct settings to the cache-control headers beforehand.