maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Michael Osipov (JIRA)" <>
Subject [jira] [Commented] (MJAVADOC-565) Make proxy configuration properly work for both HTTP and HTTPS
Date Fri, 22 Feb 2019 20:40:00 GMT


Michael Osipov commented on MJAVADOC-565:

I do not intend to fix Maven because this won't happen before 4.0 or 5.0, let's focus on this
plugin only.

bq. If an https proxy is configured but no http proxy is configured, why would you use that
proxy for non proxy hosts?  The non proxy hosts are configured per-protocol.  If you're trying
to connect using https, and there's an https proxy configured, and that proxy configuration
specifies nonProxyHosts, and you're trying to connect to one of those hosts, you should NOT
use the configured proxy.

No, it won't use non-proxy hosts from http if there is no such proxy, but the javadoc(1) requires
them to be passed as `-Dhttp.nonProxyHosts`.

You should enquire with your JDK colleagues whether they would clean that up for Java 13 or

> Make proxy configuration properly work for both HTTP and HTTPS
> --------------------------------------------------------------
>                 Key: MJAVADOC-565
>                 URL:
>             Project: Maven Javadoc Plugin
>          Issue Type: Improvement
>    Affects Versions: 3.0.1
>            Reporter: Bill Shannon
>            Assignee: Michael Osipov
>            Priority: Major
>             Fix For: 3.1.0
> There seems to be some disagreement about how to configure web proxy servers.
> Maven seems to think that the "protocol" element specifies the protocol to use when talking
to the web proxy server, and thus allows only one proxy to be configured in settings.xml. 
(Or rather, only the first configured proxy is used.)  That's not the way proxy servers work.
> The JDK configures web proxy servers based on the protocol that's being proxied.
> For example, when using a <link> to access the JDK javadocs, https is needed. 
The maven-javadoc-plugin invokes the external javadoc command with these arguments:
> {{-J-Dhttp.proxySet=true -J-Dhttp.proxyHost=<proxy-host> -J-Dhttp.proxyPort=<proxy-port>}}
> That only configures the proxy for the http protocol, not the https protocol, and thus
the linked resource can not be accessed.  To configure the proxy to be used for the https
protocol, the following arguments are needed:
> {{-J-Dhttps.proxySet=true -J-Dhttps.proxyHost=<proxy-host> -J-Dhttps.proxyPort=<proxy-port>}}

This message was sent by Atlassian JIRA

View raw message