Suppose one is connected to a company network that requires a proxy to connect to the outside world. If there's an internal IRC server one needs to connect to, the proxy should not be used, whereas it must be used to connect to any normal IRC network. Right now there's no easy way to configure that on a per-network basis, and one is forced to go to Konvi's settings and enable/disable the global proxy settings depending on the network one wants to connect to. Reproducible: Always
This is definitely planned :).
I've submitted a patch related to this issue: https://git.reviewboard.kde.org/r/116661/
Git commit 4e67d344ba9ef6f51d250e2b58de62606f5c9ceb by Anselmo L. S. Melo. Committed on 18/10/2015 at 13:15. Pushed by amelo into branch '1.6'. Allow a server to bypass the proxy settings Added an option which allows a server to bypass the proxy configured at konvi's settings -> behavior -> connection. Useful when a user needs the proxy to connect to the outside world, but should not use the proxy to connect to an internal IRC server. REVIEW: 116661 M +2 -0 src/application.cpp M +8 -1 src/irc/server.cpp M +14 -1 src/irc/serverdialogui.ui M +2 -0 src/irc/servergroupdialog.cpp M +4 -1 src/irc/serversettings.cpp M +4 -0 src/irc/serversettings.h http://commits.kde.org/konversation/4e67d344ba9ef6f51d250e2b58de62606f5c9ceb
How about when a proxy is *only* needed for a specific server? Eg, use Tor only for .onion servers...
(In reply to Luke-Jr from comment #4) > How about when a proxy is *only* needed for a specific server? Eg, use Tor > only for .onion servers... The proxy related to Tor would be configured as the global proxy (settings->configuration->connection). The patch mentioned above added a check box "use global proxy". In this case you would leave that check box marked only for the .onion servers. However, if you need a regular proxy for some servers + Tor for other ones, it is not covered.