Thank u twitter..Thank u very much. Now the issue was resolved
Regards,
George
On Mon, Oct 18, 2010 at 8:15 PM, Taylor Singletary
taylorsinglet...@twitter.com wrote:
When using headers, you need to wrap each value in quotes. The
authorization header should contain only oauth_* parameters,
Now I set to http header name is Authorization
header value =
oauth_consumer_key=**,oauth_nonce=b8qoVIxfQyEOOgu6vHjN215,oauth_signature_method=HMAC-SHA1,
oauth_timestamp=1287389017,oauth_token=*,oauth_version=1.0,page=1
,oauth_signature=cY%2F7W%2FuLWCidUD7KziKFwOcM9RI%3D
http req
could you please help me .. I am waiting for your reply...
On Mon, Oct 18, 2010 at 1:39 PM, Georgooty varghese georgo...@gmail.comwrote:
Now I set to http header name is Authorization
header value =
When using headers, you need to wrap each value in quotes. The authorization
header should contain only oauth_* parameters, not any additional query
parameters that may have been part of your request.
Here's an example of the same request you're trying to make (with different
keys, but the same
Thank u twitter.
Could you specify what is header name?
On Mon, Oct 18, 2010 at 8:15 PM, Taylor Singletary
taylorsinglet...@twitter.com wrote:
When using headers, you need to wrap each value in quotes. The
authorization header should contain only oauth_* parameters, not any
additional
Any body please help me?
On Fri, Oct 15, 2010 at 11:00 AM, Georgooty varghese georgo...@gmail.comwrote:
* Now I have removed oauth parameters in query string and added it to HTTP
header.
* Removed ~ char from auth nonce (reserved chars)
Now i got another exception Could not authenticate
* Now I set to Http header value
Header name = Authorization
value =
http://api.twitter.com/1/statuses/home_timeline.json?oauth_consumer_key=
*oauth_nonce=QyRr
The syntax of that header is wrong.
Please look at http://dev.twitter.com/pages/auth for the correct syntax.
Tom
On 10/16/10 9:23 AM, Georgooty varghese wrote:
* Now I set to Http header value
Header name = Authorization
value =
Thanks for quick reply.
Now i have removed xAuth stuff in GET parameter.
Now uri is look like
http://api.twitter.com/1/statuses/home_timeline.json?oauth_consumer_key=;
Could you give us your Base String?
Tom
On Oct 14, 2010, at 8:00 AM, Georgooty varghese georgo...@gmail.com wrote:
Thanks for quick reply.
Now i have removed xAuth stuff in GET parameter.
Now uri is look like
Base string look like
GEThttp%3A%2F%2Fapi.twitter.com
%2F1%2Fstatuses%2Fhome_timeline.jsonoauth_consumer_key%3DOmTQVOKDomNbrHuuudS
Without getting to deep into this, some advice:
* Use HTTP header based authentication instead of attaching OAuth parameters
to the query string. It makes it much more difficult to receive assistance
from others when you use query-string based auth and increases the chances
of an encoding error
* Now I have removed oauth parameters in query string and added it to HTTP
header.
* Removed ~ char from auth nonce (reserved chars)
Now i got another exception Could not authenticate you
Could u please help me..
On Thu, Oct 14, 2010 at 7:30 PM, Taylor Singletary
Don't use xAuth, use OAuth. Leave the x_auth_ stuff and use your
oauth_token and oauth_token_secret.
Oh, and look at what xAuth actually is. It's no replacement for OAuth.
Tom
On 10/14/10 5:22 AM, Georgooty varghese wrote:
Dear Twitter,
I have implemented a twitter client application in
14 matches
Mail list logo
