Purge Client

GET POST

Purges the Edgemesh® Client cache globally. Edgemesh® Client implements a stale while revalidate strategy and cached objects are revalidated on request. Purging the client cache will result in negative performance impacts while the cache is rebuilt and should be avoided if possible. Instead, let Edgemesh® automatically update the caches for the best-sustained performance.

This route is exposed as both a GET and a POST. This provides flexibility when used as a webhook endpoint. When requesting with the GET method, all request parameters are provided via search parameters. When requesting with the POST method, the request parameters are sent in the request body.

Request Parameters


REQUIRED
The hostname of the domain whose cache will be purged.

Response Properties


ok
boolean
Whether or not the request succeeded.

URL
https://api.edgemesh.com/2022-08/cache/purge/client
GETPurge Client
1curl https://api.edgemesh.com/2022-08/cache/purge/client?hostname=example.com /
2 -H 'Accept: application/json' /
3 -H 'X-API-Key: EM-0000000-0000000-0000000-0000000'
POSTPurge Client
1curl https://api.edgemesh.com/2022-08/cache/purge/client /
2 -X POST /
3 -H 'Accept: application/json' /
4 -H 'X-API-Key: EM-0000000-0000000-0000000-0000000' /
5 -d '{ "hostname": "example.com" }'
Example Response
1{
2 "ok": true
3}

Made withby Edgemesh Corporation