GeoServer Reset/Reload
Reset/Reload clears internal caches and reloads configuation from disk
Version: 1.0.0
BasePath:/geoserver/rest
All rights reserved
http://apache.org/licenses/LICENSE-2.0.html
Access
[ Jump to Models ]
Table of Contents
(deleteReload)
Invalid. Use PUT or POST to reload the catalog and configuation.
Responses
405
Method Not Allowed
(deleteReset)
Invalid. Use PUT or POST to reset the caches.
Responses
405
Method Not Allowed
(getReload)
Invalid. Use PUT or POST to reload the catalog and configuation.
Responses
405
Method Not Allowed
(getReset)
Invalid. Use PUT or POST to reset the caches.
Responses
405
Method Not Allowed
Reload the configuration from disk, and reset all caches. (postReload)
Reloads the GeoServer catalog and configuration from disk. This operation is used in cases where an external tool has modified the on-disk configuration. This operation will also force GeoServer to drop any internal caches and reconnect to all data stores.
Responses
200
OK
Reset all store, raster, and schema caches. (postReset)
Resets all store, raster, and schema caches. This operation is used to force GeoServer to drop all caches and store connections and reconnect to each of them the next time they are needed by a request. This is useful in case the stores themselves cache some information about the data structures they manage that may have changed in the meantime.
Responses
200
OK
Reload the configuration from disk, and reset all caches. (putReload)
Reloads the GeoServer catalog and configuration from disk. This operation is used in cases where an external tool has modified the on-disk configuration. This operation will also force GeoServer to drop any internal caches and reconnect to all data stores.
Responses
200
OK
Reset all store, raster, and schema caches. (putReset)
Resets all store, raster, and schema caches. This operation is used to force GeoServer to drop all caches and store connections and reconnect to each of them the next time they are needed by a request. This is useful in case the stores themselves cache some information about the data structures they manage that may have changed in the meantime.
Responses
200
OK
[ Jump to Methods ]
Table of Contents