Bug 178350

Summary:	Support for per application proxy settings
Product:	[Frameworks and Libraries] kdelibs	Reporter:	Öyvind Saether <oyvinds>
Component:	general	Assignee:	kdelibs bugs <kdelibs-bugs>
Status:	RESOLVED NOT A BUG
Severity:	wishlist	CC:	adawit
Priority:	NOR
Version:	4.1
Target Milestone:	---
Platform:	Compiled Sources
OS:	Linux
Latest Commit:		Version Fixed In:

Description Öyvind Saether 2008-12-21 07:39:49 UTC

Version:            (using Devel)
OS:                Linux
Installed from:    Compiled sources

It is currently only possible to configure a "global" proxy in KDE.

I would like proxy settings on a pr. application basis in addition to a global proxy.

Each application would/should be able to configure:

- Use global http(s) proxy
- Use global socks proxy
- Possibly any of a number of configured global proxies
- Use no proxy
- Any of a number of custom pr. application proxies

Bug #152586 indicates Amarok can do this.
Bug #168058 requests this for kget only (I would like to see it in all applications who can use a proxy, including konqueror, kget, kmail, kopete, etc)
Bug #118892 wishes to be able to use a list of proxies and switch between them.
Bug #155383 would like to be able to use proxy pr. website based on regexp (this would also be nice, not something I personally see a great use for, but I have seen a Firefox addon which adds this feature)
Bug #155707 indicates that working global proxy support for one proxy is a higher priority...
There is a comment request for pr. application proxy support in Bug #74832.

Comment 1 Dawit Alemayehu 2011-04-26 00:57:11 UTC

The ability for each application to provide their own proxy value has been in place since day one. The generic configuration that every application relies on today applies to all applications that use KIO, but they can easily override what is set through that by simply using the KIO meta data facility.

Anyhow, the point is that this is not a kdelibs issue and opening the ticket against it might be simpler, but it won't accomplish what you intended. As difficult as it may seem, you have to open this request against all the applications of your choice. Otherwise, none of the application developers will see you request, because they do not check for requests against kdelibs.