Opened 10 years ago

Closed 8 years ago

#18 closed Feature Wish (wontfix)

Make "auto-proxy" use HTTP_PROXY environment variable on *NIX platforms

Reported by: Samuli Seppänen Owned by: David Sommerseth
Priority: major Milestone: beta 2.3
Component: Networking Version: OpenVPN 2.1.0 / 2.1.1 (Community Ed)
Severity: Not set (select this one, unless your'e a OpenVPN developer) Keywords:
Cc:

Description

Currently "auto-proxy" only supports Windows. *NIX systems often store HTTP proxy settings in an environment variable called HTTP_PROXY. It would be beneficial if "auto-proxy" would detect this environment variable and use it to define proxy settings automatically.

Change History (6)

comment:1 Changed 10 years ago by Samuli Seppänen

This feature request was originally from Jason Haar and was discussed in the IRC meeting on July 8th (see https://community.openvpn.net/openvpn/wiki/IrcMeetings).

The name of the variable can also be in lowercase ("http_proxy").

For further information about HTTP_PROXY variable see these links:

comment:2 Changed 10 years ago by David Sommerseth

Milestone: beta 2.2

comment:3 Changed 10 years ago by David Sommerseth

Owner: set to David Sommerseth
Status: newaccepted

comment:4 Changed 10 years ago by Emmanuel Bretelle

Another way to detect proxy settings for users using graphical sessions could be through gconf with keys:

$ gconftool-2 -a /system/proxy

autoconfig_url =
ftp_port = 0
mode = none
secure_port = 0
secure_host =
socks_host =
socks_port = 0
ftp_host =

$ gconftool-2 -a /system/http_proxy

use_http_proxy = false
port = 8080
authentication_password =
authentication_user =
host =
use_authentication = false
ignore_hosts = [localhost,127.0.0.0/8,*.local]

Also, these might be interesting pointers:

comment:5 Changed 9 years ago by David Sommerseth

Component: Generic / unclassifiedNetworking
Milestone: beta 2.2beta 2.3

comment:6 Changed 8 years ago by David Sommerseth

Resolution: wontfix
Status: acceptedclosed

The --auto-proxy feature has been removed from OpenVPN and will be processed in the GUIs. The GUI (or another OpenVPN front-end) which is specially designed for a particular user environment will know better how to extract this information, rather than the core OpenVPN needing to support each environment separately.

Note: See TracTickets for help on using tickets.