Fix issue 15678 Key no longer appear in exception messages #15812
+80
−1
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What is the purpose of the change?
see #15678
This change introduces support for masking sensitive parameters when building URL strings in Dubbo.
Previously, parameters such as password, secretKey, or other user-defined sensitive fields could be exposed in logs or configuration outputs.
The update ensures that:
1. Sensitive parameter names can be configured through
dubbo.url.sensitive-parameter-names.
2. Any parameter matching the sensitive list is automatically excluded when the URL string is generated.
3. The behavior is covered by unit tests, ensuring consistent functionality and preventing regressions.
Checklist