Opened 10 years ago

Last modified 3 years ago

#3034 new enhancement

support for proxy auto-config scripts

Reported by: jetsaredim Owned by:
Milestone: Component: pidgin (gtk)
Version: 2.1.1 Keywords: proxy autoconfiguration
Cc: undrline, mhegeraat

Description

In many web browsers (as well as in KDE proper) there exists the ability to allow for proxy auto-configuration scripts. These scripts usually point to a URL that, when available, provide the application with the proper proxy forwarding settings for the ports involved. Though pidgin makes use of proxy settings, there is no auto-configuration setting.

An example of how this works for me in my browser is: I'm required to VPN into work to access computers on the company's internal network. They have provided a proxy auto-config script that instructs my browser to use a proxy when contacting URLs outside of the company's network and not use a proxy for those URLs inside the company. I have set the URL for this script in my browser of choice (firefox) and when I"m connected to the VPN network, the script is read and appropriately interpreted. Additionally, when I'm not connected to the VPN network, the proxy information is not available, and, as such, the browser is not able to get this information. This does not impede the normal operation of the browser in the absence of the proxy information and the user is not given any errors.

This functionality would be extremely useful in situations such as these.

Change History (13)

comment:1 Changed 10 years ago by datallah

This is doable on Windows using WinHttpGetProxyForUrl, I don't know how easy this would be to do elsewhere.

comment:2 Changed 10 years ago by raananzvi

I failed to find this bug so I opened a duplicated one (that was closed :)). This feature will be very useful to me. My work notebook is configured with auto proxy script when I'm logged to the work network and with no proxy at home. So if pidgin will be able to set the proxy automatically from the environment using the auto proxy script I will be able to seamlessly connect with pidgin both in work and at home.

comment:3 Changed 9 years ago by jashar

I recently installed the facebook plugin, which requires both ports 80 and 443. Port 80 on my network must go through a proxy, whereas 443 does not, so I need to use my pac file to designate this. Are there any plans to support this?

comment:4 Changed 8 years ago by datallah

Ticket #10122 has been marked as a duplicate of this ticket.

comment:5 Changed 8 years ago by darkrain42

Ticket #10237 has been marked as a duplicate of this ticket.

comment:6 Changed 8 years ago by Cerber

Unfortunately, my company's network layout is very different in each offices and each office uses it's own proxy server. This is not an issue for common applications as my company offers a Proxy auto conf script, but as Pidgin (or it's windows plugin) does not support PAC scripts, I must change Pidgin conf almost everyday (I work in 3 different offices). This is why PAC support would be very welcomed :)

comment:7 Changed 8 years ago by undrline

Would be helpful for me too. Any updates?

comment:8 Changed 7 years ago by TerryZhou

Any update for this? This is the only reason why I still stick to a fixed proxy, which will cause some usability issues in some cases.

comment:9 Changed 7 years ago by rekkanoryo

For the record, I believe this would be automatically fixed if we grew libproxy support.

comment:10 Changed 7 years ago by datallah

Ticket #13326 has been marked as a duplicate of this ticket.

comment:11 Changed 5 years ago by datallah

Ticket #15555 has been marked as a duplicate of this ticket.

comment:12 Changed 4 years ago by afunix

+1 for the enhancement. It is really annoying to open pidgin settings every day and turn on/off proxy..

comment:13 Changed 3 years ago by mhegeraat

+2 for the enhancement. I managed to get most programs to follow the IE proxy settings without having to restart the program and all. Pidgin is unfortunately still manual. Given the amount of duplicates,..... this bugging a lot of people.

Note: See TracTickets for help on using tickets.
All information, including names and email addresses, entered onto this website or sent to mailing lists affiliated with this website will be public. Do not post confidential information, especially passwords!