mbpurple doesn’t use provided Proxy Options

GoogleCodeExporter commented 9 years ago

What steps will reproduce the problem?
1. Using Identi.ca account
2. Configuring Proxy Options

What is the expected output? What do you see instead?
I expect that the account uses the Proxy Options, it ignores all Proxy
options, the plug-in uses global proxy options instead.

What version of the product are you using? On what operating system?
mbpurple 0.2.4, pidgin 2.5.9-r1. Gentoo.

Original issue reported on code.google.com by pablo.ro...@gmail.com on 9 Oct 2009 at 3:15

GoogleCodeExporter commented 9 years ago

+1
It's twitter with me.
---------
I'm using v0.2.4 within pidgin 2.6.3, Slackware.
I set proxy with the twitter account, the log tells me mb disregards the proxy
settings, and I can not connect to twitter(the GFW blocks twitter in China). 
Here is
the log from Pidgin debug window:
{{{
(21:32:12) account: Connecting to account xxx.
(21:32:12) connection: Connecting. gc = 0xc94480
(21:32:12) twitter: twitter_login
(21:32:12) twitter: mb_account_new
(21:32:12) twitter: creating id hash for sentid
(21:32:12) twitter: getting user/host
(21:32:12) tw_util: twitter_get_user_host
(21:32:12) tw_util: username = ##xxx##
(21:32:12) tw_util: host (config) = twitter.com
(21:32:12) twitter: user_name = xxx
(21:32:12) twitter: path = /account/verify_credentials.xml
(21:32:12) mb_net: new: create conn_data = 0x120bcd0
(21:32:12) mb_net: registered new connection data with MbAccount
(21:32:12) mb_net: NEW mb_conn_process_request, conn_data = 0x120bcd0
(21:32:12) mb_net: connecting to twitter.com on port 443
(21:32:12) mb_http: prepared packet = GET /account/verify_credentials.xml 
HTTP/1.1

Host: twitter.com

Authorization: Basic Y2hlcmlmZToyMzk0NVRSY29t

User-Agent:curl/7.18.0 (i486-pc-linux-gnu) libcurl/7.18.0 OpenSSL/0.9.8g 
zlib/1.2.3.3
libidn/1.1

Accept: */*

X-Twitter-Client: mbpidgin

X-Twitter-Client-Version: 0.1

X-Twitter-Client-Url: http://microblog-purple.googlecode.com/files/mb-0.1.xml

Connection: Close

Pragma: no-cache

(21:32:12) util: requesting to fetch a URL
(21:32:12) dns: DNS query for 'twitter.com' queued
(21:32:12) twitter: looking for twitgin
(21:32:12) twitter: registering twitgin-replying-message signal
(21:32:12) dns: Wait for DNS child 20172 failed: No child processes
(21:32:12) dns: Created new DNS child 20217, there are now 1 children.
(21:32:12) dns: Successfully sent DNS request to child 20217
(21:32:12) dns: Got response for 'twitter.com'
(21:32:12) dnsquery: IP resolved for twitter.com
(21:32:12) proxy: Attempting connection to 168.143.162.116
(21:32:12) proxy: Connecting to twitter.com:443 with no proxy //<-------------- 
I've
set a socks5 proxy for this twitter account
(21:32:12) proxy: Connection in progress
}}}

Original comment by Cherife...@gmail.com on 29 Oct 2009 at 1:43

GoogleCodeExporter commented 9 years ago

The IP addr "168.143.162.116" was manually added in /etc/hosts. In fact, DNS 
lookup
for twitter.com is hijacked here.
So, using proxy for DNS lookups is a necessary option.
Wish it'll supported.
Thanks.

Original comment by Cherife...@gmail.com on 29 Oct 2009 at 1:52

GoogleCodeExporter commented 9 years ago

I've got the same issue.

(08:54:28) jabber: jabber_actions: have pep: NO
(08:54:28) account: Connecting to account gnubot.
(08:54:28) connection: Connecting. gc = 0531E7A0
(08:54:28) twitter: twitter_login
(08:54:28) twitter: mb_account_new
(08:54:28) twitter: creating id hash for sentid
(08:54:28) twitter: getting user/host
(08:54:28) tw_util: twitter_get_user_host
(08:54:28) tw_util: username = ## xxxxxx ##
(08:54:28) tw_util: host (config) = m.twitter.com
(08:54:28) twitter: user_name = xxxxxx 
(08:54:28) twitter: path = /account/verify_credentials.xml
(08:54:28) mb_net: new: create conn_data = 04100D80
(08:54:28) mb_net: registered new connection data with MbAccount
(08:54:28) mb_net: NEW mb_conn_process_request, conn_data = 04100D80
(08:54:28) mb_net: connecting to m.twitter.com on port 443
(08:54:28) mb_http: prepared packet = GET /account/verify_credentials.xml 
HTTP/1.1

Host: m.twitter.com

Authorization: Basic Z251Ym90OjU5NjI0MjY=

User-Agent:curl/7.18.0 (i486-pc-linux-gnu) libcurl/7.18.0 OpenSSL/0.9.8g 
zlib/1.2.3.3
libidn/1.1

Accept: */*

X-Twitter-Client: mbpidgin

X-Twitter-Client-Version: 0.1

X-Twitter-Client-Url: http://microblog-purple.googlecode.com/files/mb-0.1.xml

Connection: Close

Pragma: no-cache

(08:54:28) util: requesting to fetch a URL
(08:54:28) dnsquery: Performing DNS lookup for m.twitter.com
(08:54:28) twitter: looking for twitgin
(08:54:28) twitter: registering twitgin-replying-message signal
(08:54:28) dnsquery: IP resolved for m.twitter.com
(08:54:28) proxy: Attempting connection to 46.82.174.68
(08:54:28) proxy: Connecting to m.twitter.com:443 with no proxy  // I've set up 
a
http proxy for it.
(08:54:28) proxy: Connection in progress
(08:54:49) proxy: Connecting to m.twitter.com:443.
(08:54:49) proxy: Error connecting to m.twitter.com:443 (Connection timed out.).
(08:54:49) proxy: Connection attempt failed: Connection timed out.
(08:54:49) mb_net: mb_conn_fetch_url_cb: url_data = 051D9070
(08:54:49) connection: Connection error on 0531E7A0 (reason: 0 description: 
Unable to
connect to m.twitter.com: SSL Connection Failed)
(08:54:49) mb_net: mb_conn_data_free: conn_data = 04100D80
(08:54:49) mb_net: freeing host name
(08:54:49) mb_net: freeing HTTP data->response
(08:54:49) mb_http: freeing http data
(08:54:49) mb_http: freeing header hash table
(08:54:49) mb_http: freeing self
(08:54:49) mb_net: freeing HTTP data->request
(08:54:49) mb_http: freeing http data
(08:54:49) mb_http: freeing host
(08:54:49) mb_http: freeing path
(08:54:49) mb_http: freeing header hash table
(08:54:49) mb_http: freeing fixed headers
(08:54:49) mb_http: freeing packet
(08:54:49) mb_http: freeing self
(08:54:49) mb_net: unregistering conn_data from MbAccount
(08:54:49) mb_net: freeing self at 04100D80
(08:54:49) account: Disconnecting account xxxxxx (014720A0)
(08:54:49) connection: Disconnecting connection 0531E7A0
(08:54:49) twitter: twitter_close
(08:54:49) twitter: mb_account_free
(08:54:49) twitter: 0 key removed
(08:54:49) mb_util: set_idhash output value = 
(08:54:49) twitter: destroying sent_id hash
(08:54:49) twitter: free up memory used for microblog account structure

Original comment by gonghan1...@gmail.com on 11 Feb 2010 at 9:00

GoogleCodeExporter commented 9 years ago

Same here, with Pidgin and Twitter With Windows Xp. Any Work around?

Original comment by lore.ani...@googlemail.com on 12 Feb 2010 at 9:16

GoogleCodeExporter commented 9 years ago

With 3.0  pigin crashes when using socket 
could be testet with socket server via ssh command (puty) or commandline
ssh -D 5080

Original comment by lore.ani...@googlemail.com on 14 Jun 2010 at 11:47

GoogleCodeExporter commented 9 years ago

This happens to me to i.e. mbpurple completely ignores proxy details.

e.g

(12:59:38) proxy: Connecting to api.twitter.com:443 with no proxy
(12:59:51) proxy: Connecting to api.twitter.com:443 with no proxy
(13:00:03) proxy: Error connecting to api.twitter.com:443 (No route to host).
(13:00:03) proxy: Connection attempt failed: No route to host
(13:00:03) proxy: Attempting connection to 168.143.162.109
(13:00:03) proxy: Connecting to api.twitter.com:443 with no proxy
(13:00:03) proxy: Connection in progress
(13:00:16) proxy: Connecting to api.twitter.com:443.
(13:00:16) proxy: Error connecting to api.twitter.com:443 (No route to host).
(13:00:16) proxy: Connection attempt failed: No route to host
(13:00:16) proxy: Attempting connection to 168.143.171.93
(13:00:16) proxy: Connecting to api.twitter.com:443 with no proxy
(13:00:16) proxy: Connection in progress
(13:00:29) proxy: Connecting to api.twitter.com:443.
(13:00:29) proxy: Error connecting to api.twitter.com:443 (No route to host).
(13:00:29) proxy: Connection attempt failed: No route to host
(13:00:29) proxy: Attempting connection to 128.242.240.157
(13:00:29) proxy: Connecting to api.twitter.com:443 with no proxy

Can you guys please look into this.

Thanks!

Original comment by alex.g.w...@gmail.com on 8 Jul 2010 at 5:01

GoogleCodeExporter commented 9 years ago

Original comment by andresen.nils@gmail.com on 26 Feb 2011 at 10:02

Changed state: Accepted
Added labels: Type-Enhancement
Removed labels: Type-Defect

GoogleCodeExporter commented 9 years ago

Original comment by andresen.nils@gmail.com on 30 Mar 2011 at 9:19

Changed title: mbpurple doesn’t use provided Proxy Options

GoogleCodeExporter commented 9 years ago

Issue 234 has been merged into this issue.

Original comment by andresen.nils@gmail.com on 30 Mar 2011 at 9:20

GoogleCodeExporter commented 9 years ago

Could one of you test if the patch provided in Issue#173 does fix this problem 
for you?

Original comment by andresen.nils@gmail.com on 30 Mar 2011 at 9:24

GoogleCodeExporter commented 9 years ago

If this 
(http://code.google.com/p/microblog-purple/issues/attachmentText?id=173&aid=3603
025381997214772&name=mb_http_proxy.patch&token=aee54eb21b4112ac39faf9ac0ec4d882)
 is the patch you're talking about, it's definitely not going to work as it 
doesn't reference any of the proxy parameters provided in either the account 
page, or the default pidgin proxy settings. 

The patch looks to only resolve the issue with transparent proxies.

Original comment by armen.ka...@gmail.com on 30 Mar 2011 at 9:39

GoogleCodeExporter commented 9 years ago

I am not sure, but what I understand from libpurples util.c switching from 
purple_util_fetch_url_request to purple_util_fetch_url_request_len_with_account 
in microblog/mb_net.c should make us honor proxy settings.

could someone please try the attached patch (as I have no proxy running)?

Original comment by andresen.nils@gmail.com on 15 Jun 2011 at 11:06

Attachments:

160.patch

benklop / microblog-purple

mbpurple doesn’t use provided Proxy Options #160