How to configure caching for your Edgee project
How to activate or disable caching on Edgee. Click on the image to zoom in.
3600
seconds (1 hour).
Edgee supports the following caching headers:
Surrogate-Control
: instructs Edgee to set a maximum TTL, e.g. max-age=31557600
(1 year TTL)Cache-Control
: instructs the browser to set a maximum TTL, e.g. no-store, max-age=0
(no client-side cache)Expires
: instructs the browser to cache the response until the specified data, eg. Wed, 23 October 2024 00:00:00 GMT
Age
: indicates that an object has already spent some time in an upstream cache,
which will be subtracted by the response’s max-age
to compute the maximum TTLETag
: a unique version identifier that only changes after a resource is modified, e.g. 123dq37891dc-it21
Vary
: indicates the list of headers that must match to consider a response cached, e.g. Accept-Language, User-Agent
Surrogate-Control
as Edgee can revalidate the origin response.
On the other hand, you normally want to set a shorter value (or even zero) for client-side caching
(unless it’s a static resource that changes path at each deployment, like bundled JavaScript libraries).Confirm purge all cache dialog in the Edgee console
/api/v1/users
).
Purge cache by path dialog in the Edgee console