You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
By using a custom plugin, dynamically create consumers and implement different limit count strategies on different consumers.
Because it is an online system and we do not want to change the current authentication strategy, we need to modify the existing authentication strategy in the plugin to match with a unique API key (choosing key-auth plugin), so it can match with the corresponding consumer.
The current issue is that proxy-write is not suitable for this scenario. How can we rewrite the request header?
Environment
APISIX version (run apisix version):3.9
Operating system (run uname -a):x86_64 GNU/Linux
OpenResty / Nginx version (run openresty -V or nginx -V):
etcd version, if relevant (run curl http://127.0.0.1:9090/v1/server_info):
APISIX Dashboard version, if relevant:
Plugin runner version, for issues related to plugin runners:
LuaRocks version, for installation issues (run luarocks --version):
The text was updated successfully, but these errors were encountered:
Description
By using a custom plugin, dynamically create consumers and implement different limit count strategies on different consumers.
Because it is an online system and we do not want to change the current authentication strategy, we need to modify the existing authentication strategy in the plugin to match with a unique API key (choosing key-auth plugin), so it can match with the corresponding consumer.
The current issue is that proxy-write is not suitable for this scenario. How can we rewrite the request header?
Environment
apisix version
):3.9uname -a
):x86_64 GNU/Linuxopenresty -V
ornginx -V
):curl http://127.0.0.1:9090/v1/server_info
):luarocks --version
):The text was updated successfully, but these errors were encountered: