The default proxy configuration setting for XMPP is to use the GNOME
proxy settings.  In my GNOME configuration I have configured a manual
HTTP proxy but I have not checked the 'Use the same proxy for all
protocols' checkbox.  This configuration results in pidgin attempting to
tunnel XMPP accounts through this HTTP proxy.

My expectation would be that unless I check the 'Use same proxy for all
protocols' option in the GNOME configuration XMPP would not use the HTTP
proxy configured by GNOME given a simple 'Use GNOME configuration'
selection.

I wouldn't really consider this a bug, since Pidgin will only use the
HTTP proxy from the GNOME settings and none of the others.

There are three ways of fixing the dialog that spring to mind immediately:

 - Only use the proxy if GNOME is configured to use the same proxy for
   all protocols and this option is selected or an automatic
   configuration has specified a proxy for XMPP.
 - Change the text to "Use GNOME HTTP proxy" (which is mostly what the
   option is currently doing).
 - (better variation on the same theme) alter the dialog so that when
   HTTP is selected as the proxy type there is a check box allowing the
   GNOME proxy to be selected instead of the currently visible options.

All of these would bring the function of the option closer to what
happens.

reopen 458212
thanks

As discussed in my previous reply I do feel that there is some
reasonable room for improvement in the UI here.

Subject pretty much says it all.
Even when I set my XMPP account to use no proxy, pidgin apparently still
uses the http proxy.
Note that I'm using a proxy.pac autoconfiguration file. Adding a "DIRECT"
statement there for the XMPP server allowed me to login again (looks like
privoxy breaks one of the XMPP servers I use, maybe by invalidating some
digest?)