[Pidgin] #11083: Pidgin 2.6.4 proxy problem with squid 407 response

[Pidgin]

#11083: Pidgin 2.6.4 proxy problem with squid 407 response
----------------------+-----------------------------------------------------
Reporter:  ethnopunk  |        Type:  defect   
  Status:  new        |   Component:  libpurple
 Version:  2.6.4      |    Keywords:  squide   
----------------------+-----------------------------------------------------
 I recently updated to the 2.6.4 version and after the update completed and
 I started Pidgin, I was unable to connect to any of my accounts. I use a
 remote HTTP proxy server to relay my IM connection so that restrictive
 corporate firewalls don’t block my IM accounts. I opened the debug window
 and after seeing the “Access Denied” message, I thought that it might be
 the proxy server itself. After verifying that nothing in the server
 configuration has changed recently, I started to look at other
 possibilities. I was able to configure Firefox to use the proxy server
 successfully, so I started to look at the Pidgin client as the culprit… I
 did a quick Google search and I found the reason. In the change-log for
 version 2.6.4 is a line in the libpurple component:

 * Don’t send Proxy-Authorization headers to HTTP proxy servers until we’ve
 received a “407 Proxy Authentication Required” response from the server.
 (thecrux)

 For some reason, the Squid Proxy Server that I use does not send this 407
 response back and Pidgin never sends the credentials. So of course the
 Proxy Server replies with Access Denied since it does not allow
 unauthenticated users to use it. I’m sure that the developers fix the
 problem for a good reason, but it is still frustrating that existing
 working behavior in one version stops working in the next version. Until I
 can upgrade the Squid server or figure out how to make it send the 407
 response, I’ll stay at version 2.6.3…

-- 
Ticket URL: <http://developer.pidgin.im/ticket/11083>
Pidgin <http://pidgin.im>
Pidgin