Difference between revisions of "Cache Management Web Service"
Jump to navigation
Jump to search
(→Overview) |
|||
Line 1: | Line 1: | ||
[[Category:WebService]] | [[Category:WebService]] | ||
= Overview = | = Overview = | ||
− | See [[Caching | | + | See [[Caching |Caching]] for full details. |
= Purge Cache = | = Purge Cache = |
Latest revision as of 02:42, 6 April 2022
Overview
See Caching for full details.
Purge Cache
Removes all cached information from the Fusion Cache and the front end caches (HTTP 304 responses).
Purge Cache is typically managed automatically by Fusion Registry whenever structures are modified, or if data is loaded/reindexed either automatically because new data are loaded or manually because the data is held in an external store.
It is possible however to manually purge the cache, this may be necessary if the data are held in an externally managed database. In this situation the cache should be purged every time the source data changes which does not need a full reindex , i.e. new observations are added to the database.
Entry Point | /ws/secure/settings/sendPurgeRequest |
Access | Restricted to Server Admin |
Http Method | POST |
No POST Body is required.
Response
HTTP 200 with a JSON Response:
{ Success : true }