adilalperenciftci opened a new pull request, #14177: URL: https://github.com/apache/apisix/pull/14177
### Description I traced the cache collision to the key scope omitting the effective authentication context. Identical request payloads could therefore share a cache entry even when the inbound authorization value, resolved consumer, or selected upstream instance credentials differed. I added a digest-only authentication scope covering the inbound `Authorization` header, resolved consumer name, and selected instance authentication configuration. Raw credential material never enters the cache key. Public shared-cache deployments can preserve the previous key behavior with `cache_key.auth_isolation: false`. I added integration and key-level regression coverage and documented the setting in the English and Chinese plugin references. #### Which issue(s) this PR fixes: Fixes #14151 ### Verification - `PERL5LIB=.:test-nginx/lib FLUSH_ETCD=1 prove -It/ -r t/plugin/ai-cache.t` - 235 tests passed - `make lint` - 0 warnings and 0 errors - `markdownlint-cli` on both updated plugin documents - passed ### 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 - [x] I have updated the documentation to reflect this change - [x] I have verified that this change is backward compatible -- 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]
