-
Notifications
You must be signed in to change notification settings - Fork 1.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
KeyStoreScanner is not able to monitor a symlink file and always resolves to the target. #8786
Comments
…iases Signed-off-by: Lachlan Roberts <[email protected]>
I miss why do we want to monitor the symlink, seems to make no sense to me? |
The symlink can be changed to point to a different location? |
@lachlan-roberts don't forget to set labels and projects. |
A user was requesting this feature, they wanted to modify the symlink file to point to a new target instead of just changing the target file of the symlink. We had a test for it which was wrong. So very least we should fix the test to verify the behaviour we expect. |
…er-Symlink Issue #8786 - add configuration for KeyStoreScanner to not resolve aliases
…nges + Removed changes from #8786 and #8787 + More test cases Signed-off-by: Joakim Erdfelt <[email protected]>
…nges (#9014) * Issue #8973 - Rework KeyStoreScanner handling for symlink related changes + Removed changes from #8786 and #8787 + More test cases + revert jetty.sslContext.reload.followLinks boolean + Scanner should follow its own linkOptions setting + remove bad documentation in module-ssl-reload.adoc Signed-off-by: Joakim Erdfelt <[email protected]> Signed-off-by: Lachlan Roberts <[email protected]> Co-authored-by: Lachlan Roberts <[email protected]>
This feature has been further updated as part of PR #9014 |
Jetty version(s)
9.4.x, 10.0.x, 11.0.x
Description
KeyStoreScanner
is not able to monitor a symlink file and always resolves to the target.There is a test
org.eclipse.jetty.test.KeyStoreScannerTest#testReloadChangingSymbolicLink
which is incorrectly testing that this use case works, but it is currently not possible to configure inKeyStoreScanner
.The text was updated successfully, but these errors were encountered: