We are still trying with no luck :-(. Is somebody from Twitter
listening who could help us here? I think we are making some little
mistake which is blocking us. It's really frustrating. Maybe if
somebody could check at server side and let us know if our encoding or
string formation or what might be the issue. Please help!!!!!!! Does
it matter from which region (country) we are trying to make these
calls? I hope not. We are trying this from India.
Some more things we tried:
1. We put Authorization in header as below (once with oauth_signature
encoded and once without encoded, we get two different error codes,
see below for detail):
-----Header without oauth_signature encoded
{User-Agent: Testweet
Content-Type: application/x-www-form-urlencoded
Authorization: OAuth realm="Twitter API",oauth_consumer_key="---
removed---",oauth_nonce="68f3e3ca5d7440e5bac6cbc08029d817",oauth_signature_method="HMAC-
SHA1",oauth_timestamp="1261129193",oauth_token="---
removed---",oauth_version="1.0",oauth_signature="uVAiNwVqoSa8FFqZ/HRN/
rwhod0="
}
We get following error:
{Status: 500 Internal Server Error
Vary: Accept-Encoding
Connection: close
Content-Length: 4684
Cache-Control: no-cache, max-age=300
Content-Type: text/html; charset=utf-8
Date: Fri, 18 Dec 2009 09:40:27 GMT
Expires: Fri, 18 Dec 2009 09:45:27 GMT
Set-Cookie: _twitter_sess=xxx; domain=.twitter.com; path=/
Server: hi
}
-----Header with oauth_signature encoded
{User-Agent: TestTweet
Content-Type: application/x-www-form-urlencoded
Authorization: OAuth realm="Twitter API",oauth_consumer_key="---
removed---",oauth_nonce="88b3f32da1fe46c7af8581f63e869c14",oauth_signature_method="HMAC-
SHA1",oauth_timestamp="1261129414",oauth_token="---
removed---",oauth_version="1.0",oauth_signature="h
%2FHxJ9zS0UWISrh4T2762u5paA0%3D"
}
We get following error:
{Status: 401 Unauthorized
Vary: Accept-Encoding
Connection: close
Content-Length: 148
Cache-Control: no-cache, max-age=1800
Content-Type: application/xml;
charset=utf-8
Date: Fri, 18 Dec 2009 09:44:13 GMT
Expires: Fri, 18 Dec 2009 10:14:13 GMT
Set-Cookie: _twitter_sess=xxx; path=/
Server: hi
WWW-Authenticate: Basic realm="Twitter API"
}
Thank
On Dec 15, 6:52 pm, Sanjay <shosansha...@gmail.com> wrote:
> Any Idea out there? I tried following to no avail:
>
> a. Did the entire process (starting from registering the app and
> generating consumer key/secret to getting Access Token/secret. Works
> fine till I get Access Token & Secret
> b. When I copy/paste complete URL in browser's address bar, it prompts
........
