[twitter-dev] Re: Started getting "Incorrect Signature" but I verified the signature is correct
I am actually having the same issue with the same api call. All of my
other requests work but friendships/create gives me "Incorrect
signature".
On Aug 28, 2:48 am, jmathai wrote:
> Not sure what I'm doing wrong here (but I've been doing it for 2 days
> now). I'm having trouble with a specific call. I plugged the values
> into Eran's form to validate that my signature was correct (assuming
> his form is correct). They match. Anyone else having problems with
> this?
>
> http://www.hueniverse.com/hueniverse/2008/10/beginners-gui-1.html
>
> jmat...@[~]: telnet twitter.com 80
> Trying 168.143.162.100...
> Connected to twitter.com.
> Escape character is '^]'.
> POST /friendships/create.json?id=47537461 HTTP/1.1
> Host: twitter.com
> Authorization: OAuth realm="http://twitter.com/friendships/
> create.json",oauth_consumer_key="4oaLychIwGHyFbhe4IRBUA",oauth_token="42099395-
> JS6hZgn3BMo3utA312iFITYDZkjIFTW27icq0iHFb",oauth_nonce="9235222c326d637cbfb3980dcfc5d18a",oauth_timestamp="1251441668",oauth_signature_method="HMAC-
> SHA1",oauth_version="1.0",oauth_signature="fQjwjlUSia%2BZhEFsN
> %2FXwRvCSmWM%3D"
>
> HTTP/1.1 401 Unauthorized
> Date: Fri, 28 Aug 2009 06:41:31 GMT
> Server: hi
> WWW-Authenticate: Basic realm="Twitter API"
> Status: 401 Unauthorized
> Cache-Control: no-cache, max-age=300
> Content-Type: application/json; charset=utf-8
> Content-Length: 82
> Set-Cookie: lang=en; path=/
> Set-Cookie:
> _twitter_sess=BAh7CToTcGFzc3dvcmRfdG9rZW4iLWVlODFlYzNjODJhZWUxMzNmNGQ4MzFh
> %250ANmFjNTQzMmE1OTBhMjgwNjI6CXVzZXJpBMNiggI6B2lkIiU3NTM1MmRmNzA2%250AYzUzYWU4MjBlNTdmNjYxYTBlNDFjZCIKZmxhc2hJQzonQWN0aW9uQ29udHJv
> %250AbGxlcjo6Rmxhc2g6OkZsYXNoSGFzaHsABjoKQHVzZWR7AA%253D%253D--
> b67e2c06caf9578fbc9aedba5ba7ec6a6c46afb3; domain=.twitter.com; path=/
> Expires: Fri, 28 Aug 2009 06:46:30 GMT
> Vary: Accept-Encoding
> Connection: close
>
> {"request":"\/friendships\/create.json?id=47537461","error":"Incorrect
> signature"}Connection closed by foreign host.
[twitter-dev] Re: Started getting "Incorrect Signature" but I verified the signature is correct
I'm having the same issue with the same api call. I can call
verify_credentials and get back a valid response but passing the same
details to this resource gets me the "Incorrect signature".
On Aug 28, 2:48 am, jmathai wrote:
> Not sure what I'm doing wrong here (but I've been doing it for 2 days
> now). I'm having trouble with a specific call. I plugged the values
> into Eran's form to validate that my signature was correct (assuming
> his form is correct). They match. Anyone else having problems with
> this?
>
> http://www.hueniverse.com/hueniverse/2008/10/beginners-gui-1.html
>
> jmat...@[~]: telnet twitter.com 80
> Trying 168.143.162.100...
> Connected to twitter.com.
> Escape character is '^]'.
> POST /friendships/create.json?id=47537461 HTTP/1.1
> Host: twitter.com
> Authorization: OAuth realm="http://twitter.com/friendships/
> create.json",oauth_consumer_key="4oaLychIwGHyFbhe4IRBUA",oauth_token="42099395-
> JS6hZgn3BMo3utA312iFITYDZkjIFTW27icq0iHFb",oauth_nonce="9235222c326d637cbfb3980dcfc5d18a",oauth_timestamp="1251441668",oauth_signature_method="HMAC-
> SHA1",oauth_version="1.0",oauth_signature="fQjwjlUSia%2BZhEFsN
> %2FXwRvCSmWM%3D"
>
> HTTP/1.1 401 Unauthorized
> Date: Fri, 28 Aug 2009 06:41:31 GMT
> Server: hi
> WWW-Authenticate: Basic realm="Twitter API"
> Status: 401 Unauthorized
> Cache-Control: no-cache, max-age=300
> Content-Type: application/json; charset=utf-8
> Content-Length: 82
> Set-Cookie: lang=en; path=/
> Set-Cookie:
> _twitter_sess=BAh7CToTcGFzc3dvcmRfdG9rZW4iLWVlODFlYzNjODJhZWUxMzNmNGQ4MzFh
> %250ANmFjNTQzMmE1OTBhMjgwNjI6CXVzZXJpBMNiggI6B2lkIiU3NTM1MmRmNzA2%250AYzUzYWU4MjBlNTdmNjYxYTBlNDFjZCIKZmxhc2hJQzonQWN0aW9uQ29udHJv
> %250AbGxlcjo6Rmxhc2g6OkZsYXNoSGFzaHsABjoKQHVzZWR7AA%253D%253D--
> b67e2c06caf9578fbc9aedba5ba7ec6a6c46afb3; domain=.twitter.com; path=/
> Expires: Fri, 28 Aug 2009 06:46:30 GMT
> Vary: Accept-Encoding
> Connection: close
>
> {"request":"\/friendships\/create.json?id=47537461","error":"Incorrect
> signature"}Connection closed by foreign host.
[twitter-dev] Re: Started getting "Incorrect Signature" but I verified the signature is correct
I found this thread:
http://groups.google.com/group/twitter-development-talk/browse_thread/thread/9e9bfec2f076e4f9
and tried switching my request to https instead of http and that fixed
my issue.
On Aug 28, 7:19 pm, Bill Evans wrote:
> I'm having the same issue with the same api call. I can call
> verify_credentials and get back a valid response but passing the same
> details to this resource gets me the "Incorrect signature".
>
> On Aug 28, 2:48 am, jmathai wrote:
>
> > Not sure what I'm doing wrong here (but I've been doing it for 2 days
> > now). I'm having trouble with a specific call. I plugged the values
> > into Eran's form to validate that my signature was correct (assuming
> > his form is correct). They match. Anyone else having problems with
> > this?
>
> >http://www.hueniverse.com/hueniverse/2008/10/beginners-gui-1.html
>
> > jmat...@[~]: telnet twitter.com 80
> > Trying 168.143.162.100...
> > Connected to twitter.com.
> > Escape character is '^]'.
> > POST /friendships/create.json?id=47537461 HTTP/1.1
> > Host: twitter.com
> > Authorization: OAuth realm="http://twitter.com/friendships/
> > create.json",oauth_consumer_key="4oaLychIwGHyFbhe4IRBUA",oauth_token="42099395-
> > JS6hZgn3BMo3utA312iFITYDZkjIFTW27icq0iHFb",oauth_nonce="9235222c326d637cbfb3980dcfc5d18a",oauth_timestamp="1251441668",oauth_signature_method="HMAC-
> > SHA1",oauth_version="1.0",oauth_signature="fQjwjlUSia%2BZhEFsN
> > %2FXwRvCSmWM%3D"
>
> > HTTP/1.1 401 Unauthorized
> > Date: Fri, 28 Aug 2009 06:41:31 GMT
> > Server: hi
> > WWW-Authenticate: Basic realm="Twitter API"
> > Status: 401 Unauthorized
> > Cache-Control: no-cache, max-age=300
> > Content-Type: application/json; charset=utf-8
> > Content-Length: 82
> > Set-Cookie: lang=en; path=/
> > Set-Cookie:
> > _twitter_sess=BAh7CToTcGFzc3dvcmRfdG9rZW4iLWVlODFlYzNjODJhZWUxMzNmNGQ4MzFh
> > %250ANmFjNTQzMmE1OTBhMjgwNjI6CXVzZXJpBMNiggI6B2lkIiU3NTM1MmRmNzA2%250AYzUzYWU4MjBlNTdmNjYxYTBlNDFjZCIKZmxhc2hJQzonQWN0aW9uQ29udHJv
> > %250AbGxlcjo6Rmxhc2g6OkZsYXNoSGFzaHsABjoKQHVzZWR7AA%253D%253D--
> > b67e2c06caf9578fbc9aedba5ba7ec6a6c46afb3; domain=.twitter.com; path=/
> > Expires: Fri, 28 Aug 2009 06:46:30 GMT
> > Vary: Accept-Encoding
> > Connection: close
>
> > {"request":"\/friendships\/create.json?id=47537461","error":"Incorrect
> > signature"}Connection closed by foreign host.
