search

google-code-export / microblog-purple

Automatically exported from code.google.com/p/microblog-purple
GNU General Public License v3.0
2 stars 0 forks source link

Twitter won´t work #214

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
enable plugin
enable account 

What is the expected output? What do you see instead?
messages and highlighted Icon

Grey Icon

What version of the product are you using? On what operating system?

Windows XP SP3
twitgin 0.3.0
Pidgin 2.7.3

Please provide any additional information below.

Original issue reported on code.google.com by JPRuehm...@web.de on 2 Sep 2010 at 2:30

Attachments:

GoogleCodeExporter commented 9 years ago 
I suspect this is a basic-auth issue. Twitter wants you to use OAuth. Microblog 
version 0.3.0 claims to use OAuth.

See http://code.google.com/p/microblog-purple/

pidgin 2.7.1
pidgin-mbpurple 0.2.2
Here's some info from the debug window:
(17:40:36) util: requesting to fetch a URL
(17:40:36) dns: DNS query for 'twitter.com' queued
(17:40:36) g_log: purple_account_disconnect: assertion 
`!purple_account_is_disconnected(account)' failed
(17:40:36) dns: Successfully sent DNS request to child 19560
(17:40:36) dns: Got response for 'twitter.com'
(17:40:36) dnsquery: IP resolved for twitter.com
(17:40:36) proxy: Attempting connection to 128.242.240.52
(17:40:36) proxy: Connecting to twitter.com:443 with no proxy
(17:40:36) proxy: Connection in progress
(17:40:36) proxy: Connecting to twitter.com:443.
(17:40:36) proxy: Connected to twitter.com:443.
(17:40:37) nss: subject=CN=twitter.com,OU="Twitter  Operations",O="Twitter, 
Inc.",OID.2.5.4.9="795 Folsom St, Suite 600",L=San 
Francisco,ST=California,postalCode=94107,C=US,serialNumber=4337446,OID.2.5.4.15=
Private 
Organization,OID.1.3.6.1.4.1.311.60.2.1.2=Delaware,OID.1.3.6.1.4.1.311.60.2.1.3=
US issuer=CN=VeriSign Class 3 Extended Validation SSL CA,OU=Terms of use at 
https://www.verisign.com/rpa (c)06,OU=VeriSign Trust Network,O="VeriSign, 
Inc.",C=US
(17:40:37) nss: subject=CN=VeriSign Class 3 Extended Validation SSL CA,OU=Terms 
of use at https://www.verisign.com/rpa (c)06,OU=VeriSign Trust 
Network,O="VeriSign, Inc.",C=US issuer=CN=VeriSign Class 3 Public Primary 
Certification Authority - G5,OU="(c) 2006 VeriSign, Inc. - For authorized use 
only",OU=VeriSign Trust Network,O="VeriSign, Inc.",C=US
(17:40:37) nss: subject=CN=VeriSign Class 3 Public Primary Certification 
Authority - G5,OU="(c) 2006 VeriSign, Inc. - For authorized use 
only",OU=VeriSign Trust Network,O="VeriSign, Inc.",C=US issuer=CN=VeriSign 
Class 3 Public Primary Certification Authority - G5,OU="(c) 2006 VeriSign, Inc. 
- For authorized use only",OU=VeriSign Trust Network,O="VeriSign, Inc.",C=US
(17:40:37) certificate/x509/tls_cached: Starting verify for twitter.com
(17:40:37) certificate/x509/tls_cached: Checking for cached cert...
(17:40:37) certificate/x509/tls_cached: ...Found cached cert
(17:40:37) nss/x509: Loading certificate from 
/home/x/.purple/certificates/x509/tls_peers/twitter.com
(17:40:37) certificate/x509/tls_cached: Peer cert matched cached
(17:40:37) nss/x509: Exporting certificate to 
/home/x/.purple/certificates/x509/tls_peers/twitter.com
(17:40:37) util: Writing file 
/home/x/.purple/certificates/x509/tls_peers/twitter.com
(17:40:37) certificate: Successfully verified certificate for twitter.com
(17:40:37) util: request constructed
(17:40:37) util: Response headers: 'HTTP/1.1 401 Unauthorized

Date: Thu, 02 Sep 2010 21:40:37 GMT

Server: hi

Status: 401 Unauthorized

WWW-Authenticate: OAuth realm="http://api.twitter.com"

X-RateLimit-Limit: 0

X-RateLimit-Remaining: 0

X-Runtime: 0.01038

Content-Type: application/xml; charset=utf-8

Content-Length: 123

X-RateLimit-Class: api

Cache-Control: no-cache, max-age=1800

X-RateLimit-Reset: 1283466196

Set-Cookie: k=70.22.52.253.1283463637687804; path=/; expires=Thu, 09-Sep-10 
21:40:37 GMT; domain=.twitter.com

Set-Cookie: guest_id=128346363769076295; path=/; expires=Sat, 02 Oct 2010 
21:40:37 GMT

Set-Cookie: 
_twitter_sess=BAh7CDoPY3JlYXRlZF9hdGwrCMHqZNQqAToHaWQiJTcwYjlmMWEzZGE2YmNj%250AM
DlkYTY2ZGVkNGY5ZWEwYWVhIgpmbGFzaElDOidBY3Rpb25Db250cm9sbGVy%250AOjpGbGFzaDo6Rmxh
c2hIYXNoewAGOgpAdXNlZHsA--3f78134a9c6bb618741919bcb5fe5f748319c4f5; 
domain=.twitter.com; path=/

Expires: Thu, 02 Sep 2010 22:10:37 GMT

Vary: Accept-Encoding

X-XSS-Protection: 1; mode=block

X-Frame-Options: SAMEORIGIN

Connection: close

'
(17:40:37) util: parsed 123
(17:40:37) mb_net: going to call handler
(17:40:37) connection: Connection error on 0x2c65f70 (reason: 0 description: 
Authentication error)
(17:40:37) mb_net: handler returned, retval = -1
(17:40:37) mb_net: handler return -1, retry 1
(17:40:37) mb_net: NEW mb_conn_process_request, conn_data = 0x2c662c0
(17:40:37) mb_net: connecting to twitter.com on port 443
(17:40:37) mb_http: prepared packet = GET /account/verify_credentials.xml 
HTTP/1.1

Authorization: Basic YXdncm92ZXI6cWV1aG9mdWFk

Host: twitter.com

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

Original comment by awgro...@gmail.com on 2 Sep 2010 at 10:03

GoogleCodeExporter commented 9 years ago 
I built and installed 0.3.0. It solves the problem for me.

Original comment by awgro...@gmail.com on 2 Sep 2010 at 10:23

GoogleCodeExporter commented 9 years ago 
Which authentication method is selected for the account?

Original comment by andresen.nils@gmail.com on 7 Feb 2011 at 10:14

GoogleCodeExporter commented 9 years ago 
no response in a week. 
I, too suspect "basic" authentication..
Feel free to create a new issue if that was not the case.

Original comment by andresen.nils@gmail.com on 15 Feb 2011 at 7:30