Updated list of items blocking Pidgin 2.6.0 release

Ka-Hing Cheung khc at hxbc.us
Sat Jun 6 12:57:56 EDT 2009

On Sat, 2009-06-06 at 00:16 -0400, John Bailey wrote:
> An additional item that has cropped up that I want to consider a blocker is that
> our friends over at Adium have discovered.  Due to their current beta series
> shipping libpurple 2.6.0devel, we've been getting some good testing in on the
> Yahoo 16 code.  The problem is they have users who have HTTP proxies that do not
> proxy HTTPS connections.  This means that our current proxy code fails because
> HTTP proxies seem also to be used for HTTPS.  As a result, a number of Adium
> users who were able to log in with our old auth code can no longer do so.  We
> probably need a way to explicitly indicate to the proxy code that we shouldn't
> use an HTTP proxy for an HTTPS connection (but this needs to be a flag--some
> proxies can and do proxy HTTPS), but I'm open to any suggestions.

There are more complicated scenarios as well, for example some setups
only allow certain domains to be proxied. I think it's hard to
workaround that other than have some way for the user to enter a
blacklist of domains/ports.


More information about the Devel mailing list