Suppress incorrect start-up log message related to requested URI discovery #5862
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.
Resolves #5859
Users can configure requested URI discovery explicitly as
enabled=false
with the discovery type ofHOST
. That's legitimate and is the normal case.In fact, the code creates these settings internally if the user has not set up discovery settings explicitly.
Further, in the case of the default socket, the socket init code invokes
SocketConfiguration#prepareAndCheckRequestedUriSettings
twice, and the second time through the code was incorrectly logging the message (because it had itself previously established these settings).In these cases, the code should not log the
INFO
message about ignoring explicit discovery type or trusted proxy settings when the feature is disabled.