# Zero configuration proxy support

**URL:** <https://discuss.gradle.org/t/zero-configuration-proxy-support/240>\
**Category:** Old Forum Archive\
**Created:** [March 12, 2015, 2:18pm UTC](https://discuss.gradle.org/t/zero-configuration-proxy-support/240 "2015-03-12T14:18:00Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![Francois\_Valdy](https://sea1.discourse-cdn.com/gradle/user_avatar/discuss.gradle.org/francois_valdy/32/114_2.png) [@Francois\_Valdy](https://discuss.gradle.org/u/Francois_Valdy)\
**Post date:** [March 12, 2015, 2:18pm UTC](https://discuss.gradle.org/t/zero-configuration-proxy-support/240/1 "2015-03-12T14:18:00Z")

</div>

People expect build tools to _just_ work, and requiring an extra configuration step (proxy) to have gradle work is inconvenient. Also when using a computer (laptop) in different network environments, changing settings is an extra hurdle. Finally when using [PAC](http://en.wikipedia.org/wiki/Proxy_auto-config) proxy scripts, the actual proxy being used depend on the URL, and such a setup can’t be used with a single/static proxy property.

There’s a java-level property ‘java.net.useSystemProxies’ that could be enabled (as a first step) by default, but it’s not yet perfect as it only supports manual proxy configuration (on windows at least) and not automatic/wpad ones.

## Suggestion

Gradle/Gradlew could both include the [proxy-vole](https://code.google.com/p/proxy-vole/) library, configured with OS proxy detection. Although it could be turned off (e.g. as PAC script implies javascript execution, it may be worth performance-wise to replace it by a static config, if possible), that should IMO be the default behavior, so that the builds _just_ works.

I’d be happy to contribute a PR (sounds pretty simple) should you support the idea.

## Extra

Would fix [GRADLE-2393](https://issues.gradle.org/browse/GRADLE-2393)
