DanielWu-star opened a new pull request, #13600:
URL: https://github.com/apache/apisix/pull/13600

   Previously, when limit-conn was configured at the consumer level, connection 
limits were applied per-route instead of globally per consumer. This occurred 
because the key generation concatenated ctx.conf_type and ctx.conf_version, 
which included route-specific information.
   
   This commit fixes the issue by using conf._meta.parent.resource_key for key 
generation, consistent with the same fix already applied to limit-req (#13019) 
and limit-count plugins. Now consumer-level connection limits are properly 
shared across all routes accessed by the same consumer.
   
   Changes:
   - Added gen_limit_key() function using parent.resource_key approach
   - Replaced key = key .. ctx.conf_type .. ctx.conf_version with 
gen_limit_key(conf, ctx, key) in run_limit_conn()
   - Updated test cases to match new key format
   - Added test cases (TEST 35-42) verifying consumer isolation across multiple 
routes
   
   ### Description
   
   <!-- Please include a summary of the change and which issue is fixed. -->
   <!-- Please also include relevant motivation and context. -->
   
   #### Which issue(s) this PR fixes:
   <!--
   *Automatically closes linked issue when PR is merged.
   Usage: `Fixes #<issue number>`, or `Fixes (paste link of issue)`.
   -->
   Fixes #13584
   
   ### Checklist
   
   - [x] I have explained the need for this PR and the problem it solves
   - [x] I have explained the changes or the new features added to this PR
   - [x] I have added tests corresponding to this change
   - [ ] I have updated the documentation to reflect this change
   - [x] I have verified that this change is backward compatible (If not, 
please discuss on the [APISIX mailing 
list](https://github.com/apache/apisix/tree/master#community) first)
   
   <!--
   
   Note
   
   1. Mark the PR as draft until it's ready to be reviewed.
   2. Always add/update tests for any changes unless you have a good reason.
   3. Always update the documentation to reflect the changes made in the PR.
   4. Make a new commit to resolve conversations instead of `push -f`.
   5. To resolve merge conflicts, merge master instead of rebasing.
   6. Use "request review" to notify the reviewer after making changes.
   7. Only a reviewer can mark a conversation as resolved.
   
   -->
   


-- 
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]

Reply via email to