-
Notifications
You must be signed in to change notification settings - Fork 4.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix(dao) invalidate client certificate cache when updating #8934
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Could you move the test to spec/02-integration/05-proxy/18-upstream_tls_spec.lua
? this file contains both service and upstream client cert tests.
@liverpool8056 ^, please also sign the CLA above. |
Co-authored-by: robin.xiang <[email protected]> Co-authored-by: Qirui(Keery) Nie <[email protected]>
53afe3e
to
4257248
Compare
already sign |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm from my side
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please add an entry for this PR in the CHANGELOG.md
Co-authored-by: Mayo <[email protected]>
When updating client certificate, the certificate in core_cache should be invalidation, and the corresponding cache item for the new certificate should be used. Currently this logic doesn't work.
Summary
The logic for invalidating a certificate in core_cache doesn't work when a update event occurs.
Full changelog
change the logic how to get cache_key for certificate in core_cache and add a test