[Pidgin] #9514: Can't connect to yahoo when web access is done via http proxy and port 5050 has direct access

[Pidgin]

#9514: Can't connect to yahoo when web access is done via http proxy and port 5050
has direct access
----------------------+-----------------------------------------------------
 Reporter:  cburneci  |        Owner:  marv   
     Type:  defect    |       Status:  pending
Milestone:            |    Component:  Yahoo! 
  Version:  2.5.7     |   Resolution:         
 Keywords:            |  
----------------------+-----------------------------------------------------
Changes (by cburneci):

  * status:  pending => new


Comment:

 See also #9488

 Here are the logs from the debug window:
 First, this is the case when I connect to yahoo using no proxies. First
 stage works, (scsa.msg.yahoo.com:5050), second stage fails
 (login.yahoo.com:443), because this has to be done via the proxy. I am not
 allowed to connect on http/https ports in any other way.

 {{{
 (18:26:42) account: Connecting to account cburneci
 (18:26:42) connection: Connecting. gc = 0x9979320
 (18:26:42) dns: DNS query for 'scsa.msg.yahoo.com' queued
 (18:26:42) dns: Wait for DNS child 21367 failed: No child processes
 (18:26:42) dns: Created new DNS child 21368, there are now 1 children.
 (18:26:42) dns: Successfully sent DNS request to child 21368
 (18:26:42) dns: Got response for 'scsa.msg.yahoo.com'
 (18:26:42) dnsquery: IP resolved for scsa.msg.yahoo.com
 (18:26:42) proxy: Attempting connection to 76.13.15.45
 (18:26:42) proxy: Connecting to scsa.msg.yahoo.com:5050 with no proxy
 (18:26:42) proxy: Connection in progress
 (18:26:42) proxy: Connecting to scsa.msg.yahoo.com:5050.
 (18:26:42) yahoo: 102 bytes to read, rxlen is 122
 (18:26:42) yahoo: Yahoo Service: 0x57 Status: 1
 (18:26:42) yahoo: Authentication: In yahoo_auth16_stage1
 (18:26:42) util: requesting to fetch a URL
 (18:26:42) dns: DNS query for 'login.yahoo.com' queued
 (18:26:42) dns: Successfully sent DNS request to child 21368
 (18:26:42) dns: Got response for 'login.yahoo.com'
 (18:26:42) dnsquery: IP resolved for login.yahoo.com
 (18:26:42) proxy: Attempting connection to 217.12.8.76
 (18:26:42) proxy: Connecting to login.yahoo.com:443 with no proxy
 (18:26:42) proxy: Connection in progress
 (18:26:42) proxy: Connecting to login.yahoo.com:443.
 (18:26:42) nss: Handshake failed  (-5938)
 (18:26:42) yahoo: Authentication: In yahoo_auth16_stage1_cb
 (18:26:42) yahoo: Login Failed, unable to retrieve login url: Nu s-a
 reușit conectarea la login.yahoo.com: Conexiunea SSL a eșuat
 (18:26:42) account: Disconnecting account 0xa6ec1a0
 (18:26:42) connection: Disconnecting connection 0x9979320
 (18:26:42) connection: Destroying connection 0x9979320
 (18:26:46) util: Writing file accounts.xml to directory
 /home/cburneci/.purple
 (18:26:46) util: Writing file /home/cburneci/.purple/accounts.xml
 }}}

 Gnome offers a proxy settings mechanism that Pidgin can use. There is a
 proxy setting utility that offers the posibility to specify separate
 proxies for each protocol. As you will see below, Pidgin either tries to
 use the HTTP proxy (but not HTTPS), either gives up.

 Here's the log when I try to connect using Gnome Proxy settings. In this
 case
 I have both HTTP and HTTPS proxy fields in Gnome proxy preferences window
 corrrectly filled in.
 Pidgin looks at the HTTP proxy settings and tries to use it from the very
 begining.


 {{{
 (18:35:09) connection: Connecting. gc = 0x995b3a0
 (18:35:09) dns: DNS query for 'http-proxy.xxxxxxxx' queued
 (18:35:09) dns: Wait for DNS child 21368 failed: No child processes
 (18:35:09) dns: Created new DNS child 21589, there are now 1 children.
 (18:35:09) dns: Successfully sent DNS request to child 21589
 (18:35:09) dns: Got response for 'http-proxy.xxxxxxxx'
 (18:35:09) dnsquery: IP resolved for http-proxy.xxxxxxxx
 (18:35:09) proxy: Attempting connection to 10.1.1.253
 (18:35:09) proxy: Connecting to scsa.msg.yahoo.com:5050 via http-
 proxy.xxxxxxxx:3128 using HTTP
 (18:35:09) proxy: Connection in progress
 (18:35:09) proxy: Connected to scsa.msg.yahoo.com:5050.
 (18:35:09) proxy: Using CONNECT tunneling for scsa.msg.yahoo.com:5050
 (18:35:09) proxy: Proxy server replied with:
 HTTP/1.0 403 Forbidden

 Server: squid/2.7.STABLE3

 Date: Thu, 25 Jun 2009 15:35:07 GMT

 Content-Type: text/html

 Content-Length: 1084

 Expires: Thu, 25 Jun 2009 15:35:07 GMT

 X-Squid-Error: ERR_ACCESS_DENIED 0

 X-Cache: MISS from http-proxy

 X-Cache-Lookup: NONE from http-proxy:3128

 Via: 1.0 http-proxy:3128 (squid/2.7.STABLE3)

 Connection: close
 }}}


 Now, if I clear the http proxy field and only leave the https proxy filled
 in.


 {{{
 (18:37:24) connection: Connecting. gc = 0x996e648
 (18:37:25) proxy: Gnome proxy settings are set to 'manual' but no suitable
 proxy server is specified.  Using Pidgin's proxy settings instead.
 (18:37:25) dns: DNS query for 'scsa.msg.yahoo.com' queued
 (18:37:25) dns: Wait for DNS child 21589 failed: No child processes
 (18:37:25) dns: Created new DNS child 21619, there are now 1 children.
 (18:37:25) dns: Successfully sent DNS request to child 21619
 (18:37:25) dns: Got response for 'scsa.msg.yahoo.com'
 (18:37:25) dnsquery: IP resolved for scsa.msg.yahoo.com
 (18:37:25) proxy: Attempting connection to 68.180.217.15
 (18:37:25) proxy: Connecting to scsa.msg.yahoo.com:5050 with no proxy
 (18:37:25) proxy: Connection in progress
 (18:37:25) proxy: Connecting to scsa.msg.yahoo.com:5050.
 (18:37:25) yahoo: 91 bytes to read, rxlen is 111
 (18:37:25) yahoo: Yahoo Service: 0x57 Status: 1
 (18:37:25) yahoo: Authentication: In yahoo_auth16_stage1
 (18:37:25) util: requesting to fetch a URL
 (18:37:25) proxy: Gnome proxy settings are set to 'manual' but no suitable
 proxy server is specified.  Using Pidgin's proxy settings instead.
 (18:37:25) dns: DNS query for 'login.yahoo.com' queued
 (18:37:25) dns: Successfully sent DNS request to child 21619
 (18:37:25) dns: Got response for 'login.yahoo.com'
 (18:37:25) dnsquery: IP resolved for login.yahoo.com
 (18:37:25) proxy: Attempting connection to 217.12.8.76
 (18:37:25) proxy: Connecting to login.yahoo.com:443 with no proxy
 (18:37:25) proxy: Connection in progress
 (18:37:25) proxy: Connecting to login.yahoo.com:443.
 (18:37:25) nss: Handshake failed  (-5938)
 (18:37:25) yahoo: Authentication: In yahoo_auth16_stage1_cb
 (18:37:25) yahoo: Login Failed, unable to retrieve login url: Nu s-a
 reușit conectarea la login.yahoo.com: Conexiunea SSL a eșuat

 }}}

 I think that in this case Pidgin searches the wrong place.


 Regards

-- 
Ticket URL: <http://developer.pidgin.im/ticket/9514#comment:2>
Pidgin <http://pidgin.im>
Pidgin