Headers around resource caching Back

1. Last-Modified (RESPONSE)

The last modification date of the resource, used to compare several versions of the same resource. It is less accurate than ETag, but easier to calculate in some environments. Conditional requests using If-Modified-Since and If-Unmodified-Since use this value to change the behavior of the request.

2. If-Modified-Since (REQUEST)

Makes the request conditional, and expects the resource to be transmitted only if it has been modified after the given date. This is used to transmit data only when the cache is out of date.


A unique string identifying the version of the resource. Conditional requests using If-Match and If-None-Match use this value to change the behavior of the request.

4. If-None-Match (REQUEST)

Makes the request conditional, and applies the method only if the stored resource doesn't match any of the given ETags. This is used to update caches (for safe requests), or to prevent to upload a new resource when one already exists.

5. Cache-Control (REQUEST / RESPONSE)

Directives for caching mechanisms in both requests and responses.

6. Expires (RESPONSE)

If there is a Cache-Control header with the max-age or s-maxage directive in the response, the Expires header is ignored.

The date/time after which the response is considered expired.

Empty Comments
Sign in GitHub

As the plugin is integrated with a code management system like GitLab or GitHub, you may have to auth with your account before leaving comments around this article.

Notice: This plugin has used Cookie to store your token with an expiration.