ro4i7 commented on issue #9085: URL: https://github.com/apache/apisix/issues/9085#issuecomment-1475634571
@freemankevin May be this can help: let's say we have a route in Apisix that has the following plugins configured: 1. The `response-rewrite` plugin with a priority of 10 2. The `cors plugin` with a priority of 20 In this case, the `the response-rewrite` plugin will execute before the `cors` plugin because it has a lower priority value. Now let's say we also have a consumer that has the following plugins configured: 1. The `request-rewrite` plugin with a priority of 15 2. The `rate-limiting` plugin with a priority of 25 In this case, the `request-rewrite` plugin will execute after the `response-rewrite` and `cors` plugins from the route have executed, because it has a higher priority value than the `response-rewrite` plugin but a lower priority value than the `rate-limiting` plugin. Overall means, The custom plugin priority applies to the execution order of plugins within a single phase (e.g. all plugins within the rewrite phase of a route), but not across different phases or between plugins from different sources (e.g. plugins configured on a route vs. plugins configured on a consumer). -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
