Updated list of items blocking Pidgin 2.6.0 release

[Elliott Sales de Andrade]

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
>> 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.
>>
>
> 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
(Dispatch/NS/SB).


>
> Would the flag mean that the url-fetch function would bypass the proxy for
> those connections or?
>
> ~Paul
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://pidgin.im/pipermail/devel/attachments/20090606/638282de/attachment.html>