ynsdl opened a new issue, #7872: URL: https://github.com/apache/apisix/issues/7872
### Description I want to use control rest traffic based on specific request header value. I have an header which name is X-yunus-api-key and I generate uniq value for this api-key for all my customers. I want to limit requests based on X-yunus-api-key' values. for example ; 1 customer's X-yunus-api-key: xxx 2 customer's X-yunus-api-key: yyy 3 customer's X-yunus-api-key: zzz 4 customer's X-yunus-api-key: ttt scenario; limit-req rate: 5 for xxx limit-req rate: 10 for yyy dont limit req for ttt and zzz and I have more than a hundered X-yunus-api-key. if I want to use key-auth plugin, I have to define all my api keys as a customers. But ı dont want to do that. Because our system can generate a new X-yunus-api-key for a new customer. I cant track it constantly. ### Environment - APISIX version (run `apisix version`): 2.15.0 - Operating system (run `uname -a`): Linux devops02 3.10.0-693.el7.x86_64 - OpenResty / Nginx version (run `openresty -V` or `nginx -V`): - etcd version, if relevant (run `curl http://127.0.0.1:9090/v1/server_info`): 3.4.0 - APISIX Dashboard version, if relevant: - Plugin runner version, for issues related to plugin runners: - LuaRocks version, for installation issues (run `luarocks --version`): /usr/local/bin/luarocks 3.8.0 -- 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]
