shreemaan-abhishek opened a new pull request, #14115: URL: https://github.com/apache/apisix/pull/14115
### Description When `consumer_isolation` is enabled and no APISIX consumer is resolved, `proxy-cache` falls back to `$remote_user` to partition the cache. NGINX parses `$remote_user` from the client's `Authorization: Basic` header without verifying the password, so the value is client-controlled. This PR adds a note to the `proxy-cache` docs (en and zh) clarifying that the fallback does not verify credentials and should not be relied upon to protect personalized cached responses. It recommends configuring an authentication plugin so the identity resolves to a verified consumer, or disabling caching for routes that return per-user content. #### Which issue(s) this PR fixes: N/A ### 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 - [ ] 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 (If not, please discuss on the [APISIX mailing list](https://github.com/apache/apisix/tree/master#community) first) -- 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]
