Configure an HTTP CONNECT Proxy for a Pidgin 2 Account
Select the proxy on the Pidgin account and retain the actual XMPP service as the destination.
In Pidgin 2, modify the account and open its Proxy settings. Choose HTTP for an HTTP forward proxy, enter that proxy’s host and port, and supply its account if required. SOCKS 5 is a separate choice. For a permitted public XMPP test with no proxy account configured, the HTTP proxy list supplies candidates for the HTTP fields; confirm access to the actual XMPP host and port and retain no credentials from an earlier proxy.
Use Global Proxy Settings delegates to the global configuration; an explicit account choice can differ from it. Check this field when only one account fails.
Leave the XMPP server and its service port in the protocol settings. libpurple’s HTTP proxy path uses CONNECT to request that destination connection. The office proxy must permit tunnelling to the actual XMPP port.
A successful browser request through port 8080 does not establish permission to reach an XMPP server on 5222. Likewise, connecting directly to the XMPP hostname on the proxy’s listening port does not test the proxy at all.