Updated list of items blocking Pidgin 2.6.0 release
Elliott Sales de Andrade
qulogic at pidgin.im
Sat Jun 6 03:33:34 EDT 2009
On Sat, Jun 6, 2009 at 2:52 AM, Paul Aurich <paul at darkrain42.org> wrote:
> On Jun 5, 2009, at 21:16, 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
>> shipping libpurple 2.6.0devel, we've been getting some good testing in on
>> 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
>> HTTP proxies seem also to be used for HTTPS. As a result, a number of
>> users who were able to log in with our old auth code can no longer do so.
>> probably need a way to explicitly indicate to the proxy code that we
>> use an HTTP proxy for an HTTPS connection (but this needs to be a
>> proxies can and do proxy HTTPS), but I'm open to any suggestions.
> How does this work for MSN? Shouldn't there be some group of users who
> can't log in to MSN since $FIRST_VERSION_OF_ADIUM_WITH_MSNP15?
MSNP15 doesn't use the url-fetch functions.
It connects with either purple_ssl_connect (SOAP) or purple_proxy_connect
> Would the flag mean that the url-fetch function would bypass the proxy for
> those connections or?
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Devel