Plugin

note

While configuring the same plugin, only one copy of the configuration is valid. The order of precedence is always > Route > .

While , you can declare the Plugins that are supported by the local APISIX node. This acts as a whitelisting mechanism as Plugins that are not in this whitelist will be automatically ignored. So, this feature can be used to temporarily turn off/turn on specific plugins.

In a request, a Plugin is only executed once. This is true even if it is bound to multiple different objects like Routes and Services. The order in which Plugins are run is determined by its configured priorities:

A Plugin configuration is submitted as part of the Route or Service and is placed under . It internally uses the Plugin name as the hash key to holding the configuration items for the different Plugins.

A warning level log as shown below indicates that the request was rejected by the Plugin.

APISIX Plugins are hot-loaded. This means that there is no need to restart the service if you add, delete, modify plugins, or even if you update the plugin code. To hot-reload, you can send an HTTP request through the Admin API:

For hot-reloading in stand-alone mode, see the plugin related section in stand alone mode.