fix: do not set legacy proxy from maven or env (#7072) #7074
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
aikebah
requested changes
Oct 23, 2024
maven/src/main/java/org/owasp/dependencycheck/maven/BaseDependencyCheckMojo.java
Show resolved
Hide resolved
…emylong#7074) The Apache HTTPClient based downloader supports http(s).proxy* properties, so we do not need to use legacy logic. In legacy mode http.nonProxyHosts is not honored, so setting both leads to issues due to missing proxy selectors. Omit populating legacy properties resolves this issue. In addition, we have to move the password decryption from Maven settings up, so it actually works. Signed-off-by: Stefan Kalscheuer <[email protected]>
stklcode
force-pushed
the
fix/7072-proxy
branch
from
196b029
to
e6f022b
Compare
aikebah
approved these changes
Oct 23, 2024
|
@stklcode Thanks for the PR |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Fixes Issue
#7072
Description of Change
The Apache HTTPClient based downloader supports http(s).proxy* properties, so we do not need to use legacy logic. In legeacy mode http.nonProxyHosts is not honored, so setting both leads to issues due to missing proxy selectors.
Omit populating legacy properties resolves this issue. In addition we have to move the password decryption from Maven settings up, so it actually works.
Have test cases been added to cover the new functionality?
no