[twitter-dev] Re: 'Incorrect signature' on status update with OAuth when verify credentials works
After some try and fail I finally discovered I needed a utf8_encode in the status otherwise twitter responded with the incorrect signature. Hope this helps if anyone is having the same problem. On Sep 28, 11:14 am, Angelus wrote: > Hi, > since a few days ago, my status update calls have stopped working. > They actually worked sometimes which made it even more strange. > Recently I have found a thread with some1 with the same problem I had, > and he tested the status update without accents or special characters, > and it worked. > > So I went on and tested, and it worked too. > > Why do I recieve the 'Incorrect signature' error every time I try to > update a status with accents or special characters? > What should I do? > > I'm using PHP with TwitterOAuth library and it worked fine for > everything until now :/ > > Any help is appretiated -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
Re: [twitter-dev] Re: 'Incorrect signature' on status update with OAuth when verify credentials works
hi duane. can you please share with me (and feel free to e-mail me personally) the changes you had to make? i'm not aware of any regression on our side, so i'm definitely curious. On Thu, Feb 4, 2010 at 6:43 PM, Duane Roelands wrote: > I ended up rolling back my library to an earlier version of my > encoding algorithm and things are working now. > Unfortunately, it meant sacrificing compatibility with multibyte > characters, so my library loses some functionality. > > It's frustrating to have production code fail test cases that worked > the day before. But when you don't have complete control over the > entire system, these are the things that will occasionally happen. > > Thanks for looking into it, Ryan. > > > On Feb 4, 8:35 am, ryan alford wrote: > > I just posted this status using my library with OAuth and it worked > fine.. > > > > Testing my Twitter OAuth library with some special characters > > !?:"*&^%...@!~`=+-_ > > > > Ryan > > > > On Thu, Feb 4, 2010 at 6:19 AM, Bhavani Sankar Sikakolli < > b.san...@gmail.com > > > > > > > > > wrote: > > > Yes, it fails everytime. I have checked to see that I am configuring > > > everything the right way. > > > > > On Thu, Feb 4, 2010 at 4:43 PM, ryan alford >wrote: > > > > >> Does it fail everytime? I will test mine when I get to work in about > an > > >> hour. > > > > >> Ryan > > > > >> Sent from my DROID > > > > >> On Feb 4, 2010 12:23 AM, "Duane Roelands" > > >> wrote: > > > > >> And please forgive my obnoxious tone; I'm tired and frustrated. :) > > > > >> On Feb 4, 12:05 am, Duane Roelands wrote: > > >> > Ryan: > > > > >> > If posting "Hello ... > -- Raffi Krikorian Twitter Platform Team http://twitter.com/raffi
[twitter-dev] Re: 'Incorrect signature' on status update with OAuth when verify credentials works
I ended up rolling back my library to an earlier version of my encoding algorithm and things are working now. Unfortunately, it meant sacrificing compatibility with multibyte characters, so my library loses some functionality. It's frustrating to have production code fail test cases that worked the day before. But when you don't have complete control over the entire system, these are the things that will occasionally happen. Thanks for looking into it, Ryan. On Feb 4, 8:35 am, ryan alford wrote: > I just posted this status using my library with OAuth and it worked fine.. > > Testing my Twitter OAuth library with some special characters > !?:"*&^%...@!~`=+-_ > > Ryan > > On Thu, Feb 4, 2010 at 6:19 AM, Bhavani Sankar Sikakolli > > > > wrote: > > Yes, it fails everytime. I have checked to see that I am configuring > > everything the right way. > > > On Thu, Feb 4, 2010 at 4:43 PM, ryan alford wrote: > > >> Does it fail everytime? I will test mine when I get to work in about an > >> hour. > > >> Ryan > > >> Sent from my DROID > > >> On Feb 4, 2010 12:23 AM, "Duane Roelands" > >> wrote: > > >> And please forgive my obnoxious tone; I'm tired and frustrated. :) > > >> On Feb 4, 12:05 am, Duane Roelands wrote: > >> > Ryan: > > >> > If posting "Hello ...
Re: [twitter-dev] Re: 'Incorrect signature' on status update with OAuth when verify credentials works
I just posted this status using my library with OAuth and it worked fine.. Testing my Twitter OAuth library with some special characters !?:"*&^%...@!~`=+-_ Ryan On Thu, Feb 4, 2010 at 6:19 AM, Bhavani Sankar Sikakolli wrote: > Yes, it fails everytime. I have checked to see that I am configuring > everything the right way. > > > On Thu, Feb 4, 2010 at 4:43 PM, ryan alford wrote: > >> Does it fail everytime? I will test mine when I get to work in about an >> hour. >> >> Ryan >> >> Sent from my DROID >> >> On Feb 4, 2010 12:23 AM, "Duane Roelands" >> wrote: >> >> And please forgive my obnoxious tone; I'm tired and frustrated. :) >> >> >> On Feb 4, 12:05 am, Duane Roelands wrote: >> > Ryan: >> > >> > If posting "Hello ... >> >> >
Re: [twitter-dev] Re: 'Incorrect signature' on status update with OAuth when verify credentials works
Yes, it fails everytime. I have checked to see that I am configuring everything the right way. On Thu, Feb 4, 2010 at 4:43 PM, ryan alford wrote: > Does it fail everytime? I will test mine when I get to work in about an > hour. > > Ryan > > Sent from my DROID > > On Feb 4, 2010 12:23 AM, "Duane Roelands" > wrote: > > And please forgive my obnoxious tone; I'm tired and frustrated. :) > > > On Feb 4, 12:05 am, Duane Roelands wrote: > > Ryan: > > > > If posting "Hello ... > >
Re: [twitter-dev] Re: 'Incorrect signature' on status update with OAuth when verify credentials works
Does it fail everytime? I will test mine when I get to work in about an hour. Ryan Sent from my DROID On Feb 4, 2010 12:23 AM, "Duane Roelands" wrote: And please forgive my obnoxious tone; I'm tired and frustrated. :) On Feb 4, 12:05 am, Duane Roelands wrote: > Ryan: > > If posting "Hello ...
[twitter-dev] Re: 'Incorrect signature' on status update with OAuth when verify credentials works
And please forgive my obnoxious tone; I'm tired and frustrated. :) On Feb 4, 12:05 am, Duane Roelands wrote: > Ryan: > > If posting "Hello World" works and posting "Hello world!" fails, then > the problem is not the presence or absence of the "status" parameter. > > These are libraries that were working until recently; it appears that > something has changed on Twitter's end. > > Multiple users of multiple libraries are now reporting the issue. > > On Feb 2, 11:09 pm, ryan alford wrote: > > > > > Remember that the status update is different from most of the other > > requests, because it adds the "status" parameter that is not in the other > > requests. This means that it needs to be part of the query string and also > > the signature. Leaving this out could cause an issue. > > > Ryan > > > Sent from my DROID > > > On Feb 2, 2010 10:03 PM, "ohauske" wrote: > > > Hi Ryan, > > > I tried getting the home timeline and a couple of other methods and > > everything works, everything except the update status > > > here's my request: > > >http://twitter.com/statuses/update.xml?oauth_consumer_key=**&oaut... > > > I'm using this library > > >http://code.google.com/p/oauth/ > > > On Jan 29, 6:10 am, ryan alford wrote: > > > > Try getting the home timeline and... > > > On Jan 28, 2010 11:14 PM, "arian cabezas" wrote: > > > > Hi Ryan. > > > I´m havi...
[twitter-dev] Re: 'Incorrect signature' on status update with OAuth when verify credentials works
Ryan: If posting "Hello World" works and posting "Hello world!" fails, then the problem is not the presence or absence of the "status" parameter. These are libraries that were working until recently; it appears that something has changed on Twitter's end. Multiple users of multiple libraries are now reporting the issue. On Feb 2, 11:09 pm, ryan alford wrote: > Remember that the status update is different from most of the other > requests, because it adds the "status" parameter that is not in the other > requests. This means that it needs to be part of the query string and also > the signature. Leaving this out could cause an issue. > > Ryan > > Sent from my DROID > > On Feb 2, 2010 10:03 PM, "ohauske" wrote: > > Hi Ryan, > > I tried getting the home timeline and a couple of other methods and > everything works, everything except the update status > > here's my request: > > http://twitter.com/statuses/update.xml?oauth_consumer_key=**&oaut... > > I'm using this library > > http://code.google.com/p/oauth/ > > On Jan 29, 6:10 am, ryan alford wrote: > > > > > Try getting the home timeline and... > > On Jan 28, 2010 11:14 PM, "arian cabezas" wrote: > > > Hi Ryan. > > I´m havi...
Re: [twitter-dev] Re: 'Incorrect signature' on status update with OAuth when verify credentials works
Remember that the status update is different from most of the other requests, because it adds the "status" parameter that is not in the other requests. This means that it needs to be part of the query string and also the signature. Leaving this out could cause an issue. Ryan Sent from my DROID On Feb 2, 2010 10:03 PM, "ohauske" wrote: Hi Ryan, I tried getting the home timeline and a couple of other methods and everything works, everything except the update status here's my request: http://twitter.com/statuses/update.xml?oauth_consumer_key=**&oauth_nonce=d985f559241ea3ba0fc9d6ae842e87a3&oauth_signature=hgWo0cdbttaQnUEEWkFU1USCjMc%3D&oauth_signature_method=HMAC-SHA1&oauth_timestamp=1265164536&oauth_token=***oauth_version=1.0&status=%5C%27hello%5C%27 I'm using this library http://code.google.com/p/oauth/ On Jan 29, 6:10 am, ryan alford wrote: > Try getting the home timeline and... > On Jan 28, 2010 11:14 PM, "arian cabezas" wrote: > > Hi Ryan. > I´m havi...
[twitter-dev] Re: 'Incorrect signature' on status update with OAuth when verify credentials works
Users of my library (TwitterVB) are reporting the same problem. this
library has been working for quite some time, we've made no changes to
the encoding, and now we're getting reports from several users that
statuses that contain the exclamation point ("!") are being rejected
for "incorrect signature".
I'd be grateful for some feedback from the platform team on this.
This wouldn't be the first time that OAuth was changed and no one
communicated it to the developer community.
On Feb 2, 10:02 pm, ohauske wrote:
> Hi Ryan,
>
> I tried getting the home timeline and a couple of other methods and
> everything works, everything except the update status
>
> here's my request:
>
> http://twitter.com/statuses/update.xml?oauth_consumer_key=**&oaut...
>
> I'm using this library
>
> http://code.google.com/p/oauth/
>
> On Jan 29, 6:10 am, ryan alford wrote:
>
>
>
> > Try getting the home timeline and see if you get the incorrect signature
> > message.
>
> > Ryan
>
> > Sent from my DROID
>
> > On Jan 28, 2010 11:14 PM, "arian cabezas" wrote:
>
> > Hi Ryan.
> > I´m having the same problem with the statuses/update using the php
> > library provided by Twitter, name as : Twitter-async, as said eco_bach
> > i verified my signatures and i receive information back on verify
> > credentials (and no 'incorrect signature' error), it´s really rare
> > what it´s happening couse some times it works and some times apeear
> > when a do a ¨$connection->post('statuses/update', array('status' =>
> > $statusStr))¨ the misterious message ¨incorrect signatures¨ as
> > response. I dont know what to do, becouse i´m following all the stuffs
> > that are described on the Twitter-async API. It began to happen the
> > last Tuesday 26th.
> > My regards.
> > Arian
>
> > On 27 ene, 00:30, ryan alford wrote: > It is still
> > a POST, you just don't...
>
> > > On Jan 26, 2010 4:32 PM, "eco_bach" wrote: > > Hi Ryan
> > > Changed to 'GET' and i...
[twitter-dev] Re: 'Incorrect signature' on status update with OAuth when verify credentials works
Hi Ryan,
I tried getting the home timeline and a couple of other methods and
everything works, everything except the update status
here's my request:
http://twitter.com/statuses/update.xml?oauth_consumer_key=**&oauth_nonce=d985f559241ea3ba0fc9d6ae842e87a3&oauth_signature=hgWo0cdbttaQnUEEWkFU1USCjMc%3D&oauth_signature_method=HMAC-SHA1&oauth_timestamp=1265164536&oauth_token=***oauth_version=1.0&status=%5C%27hello%5C%27
I'm using this library
http://code.google.com/p/oauth/
On Jan 29, 6:10 am, ryan alford wrote:
> Try getting the home timeline and see if you get the incorrect signature
> message.
>
> Ryan
>
> Sent from my DROID
>
> On Jan 28, 2010 11:14 PM, "arian cabezas" wrote:
>
> Hi Ryan.
> I´m having the same problem with the statuses/update using the php
> library provided by Twitter, name as : Twitter-async, as said eco_bach
> i verified my signatures and i receive information back on verify
> credentials (and no 'incorrect signature' error), it´s really rare
> what it´s happening couse some times it works and some times apeear
> when a do a ¨$connection->post('statuses/update', array('status' =>
> $statusStr))¨ the misterious message ¨incorrect signatures¨ as
> response. I dont know what to do, becouse i´m following all the stuffs
> that are described on the Twitter-async API. It began to happen the
> last Tuesday 26th.
> My regards.
> Arian
>
> On 27 ene, 00:30, ryan alford wrote: > It is still
> a POST, you just don't...
>
>
>
> > On Jan 26, 2010 4:32 PM, "eco_bach" wrote: > > Hi Ryan
> > Changed to 'GET' and i...
[twitter-dev] Re: 'Incorrect signature' on status update with OAuth when verify credentials works
Hi,
I'm having the exact same problem, but i'm using this library,
http://code.google.com/p/oauth/, I can get the tweets from the time
line, and a lot of methods work fine, but not this one
http://twitter.com/statuses/update.xml..
Here's what my request looks like,
http://twitter.com/statuses/update.xml?oauth_consumer_key=*&oauth_nonce=d985f559241ea3ba0fc9d6ae842e87a3&oauth_signature=hgWo0cdbttaQnUEEWkFU1USCjMc%3D&oauth_signature_method=HMAC-SHA1&oauth_timestamp=1265164536&oauth_token=*&oauth_version=1.0&status=%5C%27hello%5C%27
Any help would be appreciated..
On Jan 29, 6:10 am, ryan alford wrote:
> Try getting the home timeline and see if you get the incorrect signature
> message.
>
> Ryan
>
> Sent from my DROID
>
> On Jan 28, 2010 11:14 PM, "arian cabezas" wrote:
>
> Hi Ryan.
> I´m having the same problem with the statuses/update using the php
> library provided by Twitter, name as : Twitter-async, as said eco_bach
> i verified my signatures and i receive information back on verify
> credentials (and no 'incorrect signature' error), it´s really rare
> what it´s happening couse some times it works and some times apeear
> when a do a ¨$connection->post('statuses/update', array('status' =>
> $statusStr))¨ the misterious message ¨incorrect signatures¨ as
> response. I dont know what to do, becouse i´m following all the stuffs
> that are described on the Twitter-async API. It began to happen the
> last Tuesday 26th.
> My regards.
> Arian
>
> On 27 ene, 00:30, ryan alford wrote: > It is still
> a POST, you just don't...
>
> > On Jan 26, 2010 4:32 PM, "eco_bach" wrote: > > Hi Ryan
> > Changed to 'GET' and i...
Re: [twitter-dev] Re: 'Incorrect signature' on status update with OAuth when verify credentials works
Try getting the home timeline and see if you get the incorrect signature
message.
Ryan
Sent from my DROID
On Jan 28, 2010 11:14 PM, "arian cabezas" wrote:
Hi Ryan.
I´m having the same problem with the statuses/update using the php
library provided by Twitter, name as : Twitter-async, as said eco_bach
i verified my signatures and i receive information back on verify
credentials (and no 'incorrect signature' error), it´s really rare
what it´s happening couse some times it works and some times apeear
when a do a ¨$connection->post('statuses/update', array('status' =>
$statusStr))¨ the misterious message ¨incorrect signatures¨ as
response. I dont know what to do, becouse i´m following all the stuffs
that are described on the Twitter-async API. It began to happen the
last Tuesday 26th.
My regards.
Arian
On 27 ene, 00:30, ryan alford wrote: > It is still
a POST, you just don't...
> On Jan 26, 2010 4:32 PM, "eco_bach" wrote: > > Hi Ryan
> Changed to 'GET' and i...
[twitter-dev] Re: 'Incorrect signature' on status update with OAuth when verify credentials works
Hi Ryan.
I´m having the same problem with the statuses/update using the php
library provided by Twitter, name as : Twitter-async, as said eco_bach
i verified my signatures and i receive information back on verify
credentials (and no 'incorrect signature' error), it´s really rare
what it´s happening couse some times it works and some times apeear
when a do a ¨$connection->post('statuses/update', array('status' =>
$statusStr))¨ the misterious message ¨incorrect signatures¨ as
response. I dont know what to do, becouse i´m following all the stuffs
that are described on the Twitter-async API. It began to happen the
last Tuesday 26th.
My regards.
Arian
On 27 ene, 00:30, ryan alford wrote:
> It is still a POST, you just don't write the post data to the request. That
> post data is now in the query string where Twitter is expecting it.
>
> Ryan
>
> Sent from my DROID
>
> On Jan 26, 2010 4:32 PM, "eco_bach" wrote:
>
> Hi Ryan
> Changed to 'GET' and it seems I still get the Incorrect signature.
> error
>
> And the second time I try to update status, I also get 'This method
> requires a POST.' error.
Re: [twitter-dev] Re: 'Incorrect signature' on status update with OAuth when verify credentials works
It is still a POST, you just don't write the post data to the request. That post data is now in the query string where Twitter is expecting it. Ryan Sent from my DROID On Jan 26, 2010 4:32 PM, "eco_bach" wrote: Hi Ryan Changed to 'GET' and it seems I still get the Incorrect signature. error And the second time I try to update status, I also get 'This method requires a POST.' error.
[twitter-dev] Re: 'Incorrect signature' on status update with OAuth when verify credentials works
Hi Ryan Changed to 'GET' and it seems I still get the Incorrect signature. error And the second time I try to update status, I also get 'This method requires a POST.' error.
Re: [twitter-dev] Re: 'Incorrect signature' on status update with OAuth when verify credentials works
The hash algorithm can product both upper and lower case letters.. Ryan On Tue, Jan 26, 2010 at 1:53 PM, eco_bach wrote: > Also noticed, minor thing, but your signature ends in '%253d' > > Mine in uppercase '%253D' >
[twitter-dev] Re: 'Incorrect signature' on status update with OAuth when verify credentials works
Also noticed, minor thing, but your signature ends in '%253d' Mine in uppercase '%253D'
Re: [twitter-dev] Re: 'Incorrect signature' on status update with OAuth when verify credentials works
Yes, you could assume your signature creation is correct for most API calls. However, as you see with the update status API call, it has the extra parameter that is the status. Ryan On Tue, Jan 26, 2010 at 1:46 PM, ryan alford wrote: > Don't do the POST request data. You do that for Basic Auth, but not for > OAuth. > > Ryan > > > On Tue, Jan 26, 2010 at 1:44 PM, eco_bach wrote: > >> Ryan >> Since its a POST its part of my request.data. >> >> Didn't think I also needed as part of my query string but will try. >> >> >> Do you know if there is an official Twitter Oauth test page like >> >> http://developer.netflix.com/resources/OAuthTest >> or Google's? >> http://oauth.googlecode.com/svn/code/javascript/example/signature.html >> >> Tried both and getting a different signature value, so my next >> question is >> If I receive information back on verify credentials (and no 'incorrect >> signature' error), am I safe to assume my signature generation is >> corect? >> > >
Re: [twitter-dev] Re: 'Incorrect signature' on status update with OAuth when verify credentials works
Don't do the POST request data. You do that for Basic Auth, but not for OAuth. Ryan On Tue, Jan 26, 2010 at 1:44 PM, eco_bach wrote: > Ryan > Since its a POST its part of my request.data. > > Didn't think I also needed as part of my query string but will try. > > > Do you know if there is an official Twitter Oauth test page like > > http://developer.netflix.com/resources/OAuthTest > or Google's? > http://oauth.googlecode.com/svn/code/javascript/example/signature.html > > Tried both and getting a different signature value, so my next > question is > If I receive information back on verify credentials (and no 'incorrect > signature' error), am I safe to assume my signature generation is > corect? >
[twitter-dev] Re: 'Incorrect signature' on status update with OAuth when verify credentials works
Ryan Since its a POST its part of my request.data. Didn't think I also needed as part of my query string but will try. Do you know if there is an official Twitter Oauth test page like http://developer.netflix.com/resources/OAuthTest or Google's? http://oauth.googlecode.com/svn/code/javascript/example/signature.html Tried both and getting a different signature value, so my next question is If I receive information back on verify credentials (and no 'incorrect signature' error), am I safe to assume my signature generation is corect?
Re: [twitter-dev] Re: 'Incorrect signature' on status update with OAuth when verify credentials works
I still don't see your status in the query string of the URL. I see it in string for the signature, but in your actual URL, it's not there. This is my entire URL when posting a status update: http://twitter.com/statuses/update.xml?oauth_consumer_key=**&oauth_nonce=57a0d0d1-89e9-4f73-ac3d-f2f26bb2a56d&oauth_signature_method=HMAC-SHA1&oauth_timestamp=1264530600&oauth_token=36116361-8YRR4w9rRwz7HOc0nYTMmNWjCDrQdFYtnPwsiP7jm&oauth_version=1.0&status=really%20ready%20for%20the%20game%20tonight&oauth_signature=EGq5udax8bM5yuoZhJC0cIbM8uA%3d notice how my "status" is a query string parameter also. I don't see that in yours. Ryan On Tue, Jan 26, 2010 at 12:50 PM, eco_bach wrote: > Ryan > Still 'Incorrect signature' > Here's my BASE signature query string BEFORE % encoding (NOTE all > SORTED and asterisks for my consumer key!) > > > oauth_consumer_key=&oauth_nonce=16EAFA36-2A91-32A5-4A5C-6BB80EF9B45B&oauth_signature_method=HMAC- > SHA1&oauth_timestamp=1264527609&oauth_token=9353572- > G8h52Icbe0cjWIMl59fepUofRxoHzHznhzEwo9oqI&status=having some fun > getting OAuth and the Twitter api working > > > This is my final request URL, the %253D at the end of my signature > looks suspect, doubly encoded? But pretty sure worked with verify > credentials > > request.url==http://www.bitstream.ca/twitter/proxy.php?path=http%3A%2F > %2Ftwitter.com%2Fstatuses%2Fupdate.json%3Foauth_consumer_key > %3D%26oauth_nonce > %3D16EAFA36-2A91-32A5-4A5C-6BB80EF9B45B%26oauth_signature_method > %3DHMAC-SHA1%26oauth_timestamp%3D1264527609%26oauth_token%3D9353572- > G8h52Icbe0cjWIMl59fepUofRxoHzHznhzEwo9oqI%26oauth_signature > %3D5QuhEDae4gZHAxel8JVwLwkQ5J4%253D >
[twitter-dev] Re: 'Incorrect signature' on status update with OAuth when verify credentials works
Ryan Still 'Incorrect signature' Here's my BASE signature query string BEFORE % encoding (NOTE all SORTED and asterisks for my consumer key!) oauth_consumer_key=&oauth_nonce=16EAFA36-2A91-32A5-4A5C-6BB80EF9B45B&oauth_signature_method=HMAC- SHA1&oauth_timestamp=1264527609&oauth_token=9353572- G8h52Icbe0cjWIMl59fepUofRxoHzHznhzEwo9oqI&status=having some fun getting OAuth and the Twitter api working This is my final request URL, the %253D at the end of my signature looks suspect, doubly encoded? But pretty sure worked with verify credentials request.url==http://www.bitstream.ca/twitter/proxy.php?path=http%3A%2F %2Ftwitter.com%2Fstatuses%2Fupdate.json%3Foauth_consumer_key %3D%26oauth_nonce %3D16EAFA36-2A91-32A5-4A5C-6BB80EF9B45B%26oauth_signature_method %3DHMAC-SHA1%26oauth_timestamp%3D1264527609%26oauth_token%3D9353572- G8h52Icbe0cjWIMl59fepUofRxoHzHznhzEwo9oqI%26oauth_signature %3D5QuhEDae4gZHAxel8JVwLwkQ5J4%253D
[twitter-dev] Re: 'Incorrect signature' on status update with OAuth when verify credentials works
thanks will try that I know there is the beginners guide to OAuth on the OAuth site, but came across this excellent walkthru on Vimeo's site http://www.vimeo.com/api/docs/oauth
Re: [twitter-dev] Re: 'Incorrect signature' on status update with OAuth when verify credentials works
You need to have the parameter name and value. Ryan Sent from my DROID On Jan 25, 2010 11:47 PM, "eco_bach" wrote: Thanks Ryan I'll have to look into signature creation more closely. Essentially, if I understand correctly, I am most likely missing the "status" parameter BEFORE creating the signature. Would I need to include the status value as well, or is only the parameter name necessary to create the signature?
[twitter-dev] Re: 'Incorrect signature' on status update with OAuth when verify credentials works
Thanks Ryan I'll have to look into signature creation more closely. Essentially, if I understand correctly, I am most likely missing the "status" parameter BEFORE creating the signature. Would I need to include the status value as well, or is only the parameter name necessary to create the signature?
