[WAGON-423] Add support of .pac file for proxy configuration

[jira-importer]

Emmanuel Venisse opened WAGON-423 and commented

Authorize Proxy Auto-Config File (.pac file) for proxy configuration in user model.
http://wp.netscape.com/eng/mozilla/2.0/relnotes/demo/proxy-live.html

=>Use rhino for read the pac file.

---

Issue Links:

• MNG-5879 Add autoproxy support
  ("is duplicated by")

7 votes, 8 watchers

[jira-importer]

Brett Porter commented

not blocking alpha-1.

[jira-importer]

Brett Porter commented

earlier if we can get it, but not a high enough priority to fit alpha-2 either

[jira-importer]

Rahul Akolkar commented

Hi,
Is anyone working on this one ? If not, I can pick this up. Could someone let me know how we intended to go about this, i.e. I am not sure about what the 'user model' in the firs comment pertains to?

Thanks,
Rahul

[jira-importer]

Brett Porter commented

nobody is working on it presently. I'd place the URL in the <proxy> element in settings.xml.

[jira-importer]

Rahul Akolkar commented

another resource:
http://java.sun.com/j2se/1.4.2/docs/guide/plugin/developer_guide/proxie_config.html#automatic

[jira-importer]

Brett Porter commented

needs votes

[jira-importer]

Ryan Lea commented

Hi,

I'm currently worrking on a project that is currently using ant for builds. I'd like to propose an option of switching to mvn. A main driver of this is to take advantage of the features supplied in TeamCity, which aren't fully available in ant.

Would be great if this was done!

[jira-importer]

Dennis Kieselhorst commented

Very useful. Any news on this?

[jira-importer]

Jason van Zyl commented

Please refer to https://cwiki.apache.org/confluence/display/MAVEN/The+Great+JIRA+Cleanup+of+2014

[jira-importer]

Jason van Zyl commented

Please refer to https://cwiki.apache.org/confluence/display/MAVEN/The+Great+JIRA+Cleanup+of+2014 if you're wondering why this issue was closed out.

[jira-importer]

Edwin Wiles commented

Please reopen. Proxy configuration is one of the most irritating failures in Maven. If Proxies could be specified in profiles, that would be better than nothing. But being able to use the same proxy pac file as everything else would be excelent.

[jira-importer]

Michael Osipov commented

Edwin,

why can't you simply provide the appropriate proxy hostname?

[jira-importer]

Edwin Wiles commented

I work with a team that has contractors from two companies on it. Between those people, we have the following situations:

1. Company A's network, with company A's Proxy, and company A's Nexus mirror.
2. Company B's network, ditto.
3. Company A's VPN, with a different Proxy, and maybe access to the mirror.
4. Company B's VPN, ditto.
5. Home Network with Proxy
   1. ...without Mirror.
   2. ...with Mirror
6. Home Network without Proxy
   1. ...without Mirror.
   2. ...with Mirror.

This is a mobile workforce, any of these people can be in pretty much any of these situations. A single source for all of them (a Proxy PAC) file, would go a LONG way to reducing the problem.

And before you can say "well if you have a mirror, you don't need the proxy", don't ever think that. There are still things that get done inside the Maven Java instance that require Proxy access that doesn't go through the mirror.

I tried putting the proxies and/or mirrors into properties in profiles, and having the proxy and mirror setup done via those properties. It didn't work at all.

I've actually filed another ticket, one asking for both Proxies and Mirrors to be added to the list of things you can put inside Profiles. In some respects, that would be an even better solution, but the PAC solution appeared to have some code already associated with it, and was therefore more likely to be implemented sooner.

Even if we get the Proxies and Mirrors inside Profiles, the ability to use the PAC files would still be useful. That way, when corporate network management makes a change to the proxies, we'd pick it up automatically.

[jira-importer]

Michael Osipov commented

Proxies and mirrors won't get into profiles that fast because that would require a model change. Not possible before Maven 4. Regarding the PAC, I do understand your pain. We do you PACs too but luckily, I am happy with just the proxy name.

Using the PAC file depends on the Wagon transport used for HTTP. See here. One can pass custom attributes to a transport in the settings.xml without changing the model. So the options are improve the lightweight transport or create a JIRA issue with Apache HTTP Client for PAC Proxy support and provide a fix. Then this can be used with Maven.

What do you think? If this sounds reasonable, I would move this issue to Wagon.

[jira-importer]

Edwin Wiles commented

I think it sounds quite reasonable, and would be a large step towards improving Maven's handling of proxies.

Many Thanks!