maven-issues mailing list archives

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


Bill Shannon commented on MJAVADOC-565:

I don't know what the rationale was for only specifying nonProxyHosts for http and having
it apply to https as well.  If you think that's a problem, feel free to file a bug against

I guess I misinterpreted your statement.  I think what you meant is that if there's an https
proxy configured but no http proxy configured, you'll take the nonProxyHosts from the https
proxy configuration and pass it to the javadoc tool using -Dhttp.nonProxyHosts.  That makes

I'd love to know why someone would proxy https but not http, or vice versa.

> 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