[
https://jira.codehaus.org/browse/MNG-2305?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=353558#comment-353558
]
Gordon Pettey edited comment on MNG-2305 at 1/28/15 2:11 PM:
-------------------------------------------------------------
Either there has been regression out this was closed erroneously. This behavior
is still exhibited in maven 3.2.3 - 3.2.5.
When a single <protocol>http</procotol> proxy is configured in settings, access
to HTTPS URLs (e.g.
https://commons.apache.org/proper/commons-collections/javadocs/api-release/)
fails. If the proxy in settings.xml is set <active>false</false>, and I specify
-Dhttp.proxy{Host,Post,User,Password} on the mvn command line, everything works
fine. mvn -X claims to be passing only -J-Dhttp.proxy options to javadoc.exe
via command line, but https.proxy properties are clearly being set somehow when
they shouldn't be.
was (Author: petteyg):
Either there has been regression out this was closed erroneously. This behavior
is still exhibited in maven 3.2.3.
> only first active proxy considered/used
> ---------------------------------------
>
> Key: MNG-2305
> URL: https://jira.codehaus.org/browse/MNG-2305
> Project: Maven
> Issue Type: Bug
> Components: General
> Affects Versions: 2.0.4, 2.1.0-M1
> Environment: WIN2K JDK 1.5.0_06
> proxy:81 for both http and https
> Reporter: Franz Fehringer
> Assignee: Benjamin Bentmann
> Fix For: 3.0-alpha-3
>
> Attachments: settings.xml
>
>
> With the attached settings.xml
> all https connects fail (doing mvn -U).
> If i reverse the order (https first http second) all http connects fail.
> Questions:
> Does https tunneling over http proxies work at all with Maven2 (sending HTTP
> CONNECT <remote address> to the proxy is needed)?
> Why is the Java system configuration (in Application
> Data\Sun\Java\Deployment\deployment.properties) not used to detect proxies?
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
