[twitter-dev] Re: Incorrect signature

Hello again, Solved it. Reading pages upon pages of chats here helped... thanks for that. As I suspected, the answer will boil down to a simple thing, and indeed it was. I found that having spaces in the text was causing the problem so I removed these in my test and bingo, all worked. However,

[twitter-dev] Re: incorrect signature with get parameters

Hi Arnaud, Thanks for answering so quickly. It stil does not work when using http but it does work perfectly when using https ! Thx On May 24, 10:43 pm, Arnaud Meunier wrote: > Hey there, > > The URL you're passing to your getBaseString function is not correct. The > correct endpoint to ReTweet

Re: [twitter-dev] Re: incorrect signature with get parameters

Hey there, The URL you're passing to your getBaseString function is not correct. The correct endpoint to ReTweet a tweet is "/1/statuses/retweet/:id" (cf http://dev.twitter.com/doc/post/statuses/retweet/:id). Also remove the "id" part in your parameters. Arnaud / @rno

[twitter-dev] Re: incorrect signature with get parameters

I've tried using POST and GET method. And i've seen the "htts: mistake, but doesn't change anything. :( On May 24, 2:25 pm, galeyte wrote: > Hi again ! > > I'me still working on my javascript twitter client. > At this time, every request i make using POST method work perfectly, > but i'm experien

[twitter-dev] Re: Incorrect Signature errors with both Tweepy and python-twitter

your welcome - glad you found a solution! -- 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:/

[twitter-dev] Re: Incorrect Signature errors with both Tweepy and python-twitter

Regenerating the keys did the trick. Turns out there is a bug in the Django app that I'm using for Twitter authentication that uses stale access tokens. Updating the user's access token whenever he/she logs into my app fixed the issue. Also, apigee.com has a really good Twitter API panel. Thanks

[twitter-dev] Re: Incorrect Signature errors with both Tweepy and python-twitter

Here is what I see: send: u'GET /1/account/verify_credentials.json?oauth_nonce=85271670&oauth_timestamp=1303621152&oauth_consumer_key=...&oauth_signature_method=HMAC-SHA1&oauth_version=1.0&oauth_token=...&oauth_signature=... HTTP/1.1\r\nAccept-Encoding: identity\r\nHost: api.twitter.com\r\nCon

[twitter-dev] Re: Incorrect Signature errors with both Tweepy and python-twitter

I receive a HTTP 401 Unauthorized code. I've made sure the twitter user gives the app read/write permissions. I've also made sure the user isn't being rate limited. Here's the POST request with PII removed. send: 'GET /1/account/verify_credentials.json? oauth_nonce=95746995&oauth_timestamp=1303607

[twitter-dev] Re: Incorrect Signature errors with both Tweepy and python-twitter

I just ran the following test using my current source tree for python-twitter and got no errors. You may want to use debugHTTP=True to look at what the POST being sent to Twitter is. import twitter api = twitter.Api(consumer_key='', consumer_secret='', access_t

Re: [twitter-dev] Re: Incorrect signature

Hi Thomas, The timestamp must be the current time in epoch seconds. By design the epoch time is in GMT, which is the same as Twitter's servers so you shouldn't need to adjust it. If you do it implies your server clock isn't set correctly. Looking at your code you have a lot going on which increas

[twitter-dev] Re: Incorrect signature

I just tried using time() without adding 3 hours and I get this error: Timestamp out of bounds So I believe adding 3 hours is the right thing to do. On Jan 17, 9:36 pm, Yusuke Yamamoto wrote: > Hi, > > time() returns epoch time which is an absolute value, and you don't need to > consider timezon

Re: [twitter-dev] Re: Incorrect signature

Hi, time() returns epoch time which is an absolute value, and you don't need to consider timezones. http://php.net/manual/en/function.time.php -- Yusuke Yamamoto yus...@mac.com this email is: [x] bloggable/tweetable [ ] private follow me on : http://twitter.com/yusukeyamamoto subscribe me at :

[twitter-dev] Re: Incorrect signature

My servers default time is PST but twitters time is EST I believe so that's why I added 3 hours. On Jan 17, 4:35 pm, "@epc" wrote: > On Jan 16, 2:10 pm, Thomas wrote: > > > > $time = time() + 10800; > > Why are you setting the timestamp for 3 hours in the future? > oAuth/twitter are very picky

[twitter-dev] Re: Incorrect signature

On Jan 16, 2:10 pm, Thomas wrote: > $time = time() + 10800; > Why are you setting the timestamp for 3 hours in the future? oAuth/twitter are very picky about the time being "close" to accurate, being 3 hours off is definitely one potential problem with your code. -- -ed costello -- Twitter dev

[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

[twitter-dev] Re: Incorrect signature with oAuth

Hi Carlos: It works!!! Thanks for the tips. I set the header to the one one the GoogleCode page. I also removed the spaces in the header. I was getting the same signature as the GoogleGode page (Im using pure C++ here so I have a set of libs for SHA/Base64) so there was some concern. While C++

[twitter-dev] Re: Incorrect signature with oAuth

Don't know if it matters but you are adding a space after each comma in the Authorization Header. Also check your signature generation method using the following: http://oauth.googlecode.com/svn/code/javascript/example/signature.html and see if you are getting the same signature values. On Jul 17

[twitter-dev] Re: Incorrect signature with oAuth

Hi Carlos: Thanks for the sniplet. I just converted my source to encode when *building* the parameter string and encode again when *adding* it. I tried on my proper app token codes and still signature error. This is with my base looks like now. NOTE: I changed the C++ source back to the older t

[twitter-dev] Re: Incorrect signature with oAuth

Are you doing this in PseudoCode? base = "method&URLEncode(endpoint)&URLEncode(URLParameterString)" where URLParameterString = "URLEncode(name)=URLEncode(value)&URLEncode(name)=URLEncode(value)..." On Jul 17, 11:01 am, CeBeans wrote: > Im developing a DLL in eVC++3.0 (native C++) that uses the

[twitter-dev] Re: Incorrect Signature for oAuth

Thanks to all your replies helped I can now perform status updates via oAuth. I'm rather irritated that Uri.EscapeDataString doesn't escape all illegal characters. It just fails now if a status update contains exclamation marks, asterisk, dollar signs, single quotes and probably a few more. I'll

[twitter-dev] Re: Incorrect Signature for oAuth

Hi Rhys, - you're right status should be at the end of the base string. Even though it's sent as a POST, it still has to go in alpha order in the base string. - Also be careful of the leading %3F you've got after the update.xml - should just be (method)&(baseURL+service)&(list of params separated b

[twitter-dev] Re: Incorrect Signature for oAuth

Hi, thanks to you both. I've removed the source parameter. There is something wrong with my signature base indeed. Here's what I am sending for a status update... POST&http%3A%2F%2Fapi.twitter.com%2F1%2Fstatuses%2Fupdate.xml&%3Fstatus %3Dtest%26oauth_consumer_key%3Dxx%26oauth_

Re: [twitter-dev] Re: Incorrect Signature for oAuth

To help you debug, it would be useful to see the signature base string that was generated for the request. Possible things going wrong: the signature base string isn't mentioning that this is a POST, or your OAuth-based parameters are leaking into your POST body.. As Hwee-Boon said, you also needn

[twitter-dev] Re: Incorrect Signature for oAuth

Since it's GET works and POST, no. 1 reason is to make sure the base URI in the base signature string is constructed correctly. In your example, you don't need source= since it's OAuth. -- Hwee-Boon On Jun 6, 8:56 pm, rhysmeister wrote: > Hi All, > > I am having problems identifying what is

[twitter-dev] Re: Incorrect signature when calling update url /1/statuses/update.xml

Thanks Taylor and Mike.. my hours of heartache are solved :) On May 21, 3:03 am, Taylor Singletary wrote: > Mike Dice gets the dice :) Glad you figured it out. > > The best way to think of this is that a POST body being sent to Twitter is > by definition URL Escaped when valid. The OAuth spec ask

Re: [twitter-dev] Re: Incorrect signature when calling update url /1/statuses/update.xml

Thanks a lot Cameron! I was just sitting down to write my lib, planning on doing as you suggest below. On Thu, May 20, 2010 at 5:06 PM, Cameron Kaiser wrote: > > I will write my own if I have to. But before I do, I'd like to understand > as > > many details as possible about the specifics of Twit

Re: [twitter-dev] Re: Incorrect signature when calling update url /1/statuses/update.xml

> I will write my own if I have to. But before I do, I'd like to understand as > many details as possible about the specifics of Twitter's RFC 3986 behavior. This is the regex I'm using, which is known to work: $x =~ s/([^-0-9a-zA-Z._~])/"%".uc(unpack("H2",$1))/eg; In short, letters, num

Re: [twitter-dev] Re: Incorrect signature when calling update url /1/statuses/update.xml

I will write my own if I have to. But before I do, I'd like to understand as many details as possible about the specifics of Twitter's RFC 3986 behavior. In my experience with RFC specs, they usually provide a lot of detail but they almost always leave some of those details to be interpreted by imp

Re: [twitter-dev] Re: Incorrect signature when calling update url /1/statuses/update.xml

my code 401 . From: Cameron Kaiser To: twitter-development-talk@googlegroups.com Sent: Thu, May 20, 2010 1:28:44 PM Subject: Re: [twitter-dev] Re: Incorrect signature when calling update url /1/statuses/update.xml > FYI - I am writing a .Net ba

Re: [twitter-dev] Re: Incorrect signature when calling update url /1/statuses/update.xml

> FYI - I am writing a .Net based library and so I currently use > System.Uri.EscapeDataStringto > do my escaping I don't know what that routine is, but if it's not RFC 3986 compliant, it won't work. You might want to roll y

[twitter-dev] Re: Incorrect signature when calling update url /1/statuses/update.xml

Taylor, I am having a very similar problem. I think I am missing some crucial point about the encoding method that needs to be used with twitter. THe library I am working on has successfully authenticated using Oauth with twitter. I have my access_token and access_token_secret and I want to update

Re: [twitter-dev] Re: Incorrect signature when calling update url /1/statuses/update.xml

Hi Onn, It's best to consider all space characters as %20 when building both your POST body and signature base string -- instead of using " " or "+", just get right down to it as "%20". I'll show you how a pretty varied string of characters would be correctly encoded both for the POST body and si

[twitter-dev] Re: Incorrect signature when calling update url /1/statuses/update.xml

Hi Taylor, I am using Curl to update status. I use POST method. The new status is not included in the headers, but is included in the POST body and in the signature base string. Also (and this Curl does automatically for me) I am sending the following header: Content-Type: application/x-www-

Re: [twitter-dev] Re: Incorrect signature when calling update url /1/statuses/update.xml

Good to hear that you got it working! :D Oh and it's "Pablo" by the way, hehehe. On Mon, May 17, 2010 at 1:34 PM, Gero wrote: > Got it solved now. I upgraded to the 0.6.6 version and added the > status update as a body parameter (instead of header). (Pable gave me > that tip). > > The working (

[twitter-dev] Re: Incorrect signature when calling update url /1/statuses/update.xml

Got it solved now. I upgraded to the 0.6.6 version and added the status update as a body parameter (instead of header). (Pable gave me that tip). The working (Scala) code is now: val accessToken2 = scribe.getAccessToken(new Token(token, tokenSecret), oaverifier) val request2 = new Requ

Re: [twitter-dev] Re: Incorrect signature when calling update url /1/statuses/update.xml

Indeed it was solved in version 0.6.6. Sorry for that Gero! On Mon, May 17, 2010 at 9:46 AM, Taylor Singletary < taylorsinglet...@twitter.com> wrote: > Hi Gero, > > This particular issue looked to have been caused by a quirk in the way that > the Scribe library was encoding spaces. The library h

Re: [twitter-dev] Re: Incorrect signature when calling update url /1/statuses/update.xml

Hi Gero, This particular issue looked to have been caused by a quirk in the way that the Scribe library was encoding spaces. The library has since been updated by the author. However, if you're still having the issue in another implementation, I'll be happy to help. Can you share the POST body of

[twitter-dev] Re: Incorrect signature when calling update url /1/statuses/update.xml

Hi, Any updates on this issue? I'm running into the same problem and have not yet been able to resolve it. Regards, Gero On May 1, 12:42 am, Taylor Singletary wrote: > Hi Pablo, > > Thanks for chiming in about Scribe. I'll take a look again soon at Scribe > and see if I can ascertain its potent

Re: [twitter-dev] Re: Incorrect signature when calling update url /1/statuses/update.xml

Hi Pablo, Thanks for chiming in about Scribe. I'll take a look again soon at Scribe and see if I can ascertain its potential fault (or our own if that is the case). Keep up the good work on your OAuth library, Pablo! :) Taylor Singletary Developer Advocate, Twitter http://twitter.com/episod On

[twitter-dev] Re: Incorrect signature when calling update url /1/statuses/update.xml

Hi Taylor! I believe Rahul is having this problem while using my library (http:// github.com/fernandezpablo85/scribe) I've tested myself, I'm pretty sure the error lies in my code but I can't tell why :S Here's the string that gets signed and the OAuth header in case that helps! String to sign

[twitter-dev] Re: Incorrect signature when calling update url /1/statuses/update.xml

Taylor, Here you go. I have tried adding the content type as follows. conn.setRequestProperty("Content-Type", "application/x-www-form- urlencoded"); But this doesn't help at all and i still continue receiving the same error of incorrect signature. Any guess? Thanks, Rahul On Apr 29, 9:03 pm,

[twitter-dev] Re: Incorrect signature when calling update url /1/statuses/update.xml

Taylor, I am presently using scribe java library for OAuth and as you said all spec compliant libraries the signature base string will only contain POST body parameter so does this one. Also I will try to add the header 'Content-Type' to the library and let you know how it goes. Thanks, Rahul

Re: [twitter-dev] Re: Incorrect signature when calling update url /1/statuses/update.xml

Whether it matters before creating your signature or not depends entirely on the OAuth library you are using. In spec-compliant OAuth libraries, the signature base string will only contain POST body parameters when they are of the application/x-www-form-urlencoded type -- most OAuth libraries need

[twitter-dev] Re: Incorrect signature when calling update url /1/statuses/update.xml

So what are trying to say is that i should explicitly add Content-type header in the message going out and that too before creating the signature? Thanks, Rahul On Apr 29, 4:58 pm, Taylor Singletary wrote: > Since you're sending a status, you should be setting a Content-Type header > to indicate

Re: [twitter-dev] Re: Incorrect signature when calling update url /1/statuses/update.xml

Since you're sending a status, you should be setting a Content-Type header to indicate the type of payload -- it's best never to assume that a HTTP server or a HTTP library will know how to understand a payload without being explicitly told what kind of payload that is. The signature might be mis-c

[twitter-dev] Re: Incorrect signature when calling update url /1/statuses/update.xml

Hello, To answer your questions. The following is the body response i receive back /1/statuses/update.xml Incorrect signature Also, I am not setting any content type header at this point & I am using "POST" only for token negotiation. and have not tried any get restricted resource yet. I

Re: [twitter-dev] Re: Incorrect signature when calling update url /1/statuses/update.xml

Hi Rahul, I'm trying to think of other reasons. We might be throwing the invalid signature error in a case where the signature is not in fact invalid. How about requests are not of the type POST? Have you had a GET (other than OAuth token negotiation steps) work for you? When you were doing the t

[twitter-dev] Re: Incorrect signature when calling update url /1/statuses/update.xml

Taylor, A quick update on this. I tried generating the signature from my library and the page mentioned below they both seems tbe exactly the same. http://hueniverse.com/2008/10/beginners-guide-to-oauth-part-iv-signing-requests/ What else can be the reason and how come twitter is responding

[twitter-dev] Re: Incorrect signature when calling update url /1/statuses/update.xml

Any Clues or suggestions ? Thanks, Rahul On Apr 29, 1:19 pm, Rahul wrote: > Taylor, > > Thanks for taking a look at it. and to answer your question yes I do > pass the status in the signature basetring. > > Also below is my string which i pass to the below mentioned toSign > variable. > > toSign

[twitter-dev] Re: Incorrect signature when calling update url /1/statuses/update.xml

Taylor, Thanks for taking a look at it. and to answer your question yes I do pass the status in the signature basetring. Also below is my string which i pass to the below mentioned toSign variable. toSign: POST&https%3A%2F%2Fapi.twitter.com%2F1%2Fstatuses %2Fupdate.xml&oauth_consumer_key%xxx

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

[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 th

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 configu

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

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

[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

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

[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 signat

[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=hgWo0cdbttaQnUEEWkFU

[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/up

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 e

[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

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

[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

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 o

[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/

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

[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=935357

[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 sig

[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 signatur

[twitter-dev] Re: "Incorrect signature" returned for Lists API

Michael, You're actually right. Didn't think about strtolower fixing the camel casing issue. Have a look at the last test case in EpiTwitterTest.php for example usage. I'll get around to increasing documentation soon (I hope). On Nov 2, 10:18 pm, Michael Steuer wrote: > Hi Jaisen, > > Doesn'

[twitter-dev] Re: "Incorrect signature" returned for Lists API

Hi Jaisen, Doesn't Nelu's use of strtolower take care of your camel case concern? I just posted a comment on your blog - it'd be great if you could publish a couple lines around usage of your lib with the new lists URL structure etc. Thanks so much, Michael. On 11/2/09 9:51 PM, "jmathai" w

[twitter-dev] Re: "Incorrect signature" returned for Lists API

Nelu, While that works, I suggest using the ID over the username since a username with camel case will break the path regex. This should work with the newest version of the library from Github. I'm considering including an option to pass in the url as a string in the 2.0 version of the library.

[twitter-dev] Re: "Incorrect signature" returned for Lists API

And an update fot the EPI library: http://bit.ly/3KODt1 On Nov 2, 10:53 am, Nelu Lazar wrote: > Figured the answer for the issue above, for @jmathai's EPITwitter > library, here is the call code that works: > > $twitterOAuthObj->{'get_'.(string)strtolower > ($username).'ListsMemberships'}(array

[twitter-dev] Re: "Incorrect signature" returned for Lists API

Figured the answer for the issue above, for @jmathai's EPITwitter library, here is the call code that works: $twitterOAuthObj->{'get_'.(string)strtolower ($username).'ListsMemberships'}(array(...)); - @NeluLazar On Nov 2, 10:37 am, Nelu Lazar wrote: > I am experiencing "Incorrect signature" r

[twitter-dev] Re: Incorrect signature ERROR on /statuses/update.xml - Help Please....

I am having the exact same problem! On Jul 29, 5:22 am, Brett Hellman wrote: > Request > URL:https://twitter.com/statuses/update.xml?STATUS=oauthtestingpleasework... > > > > >   > /statuses/update.xml?STATUS=oauthtestingpleasework&oauth_consumer_key=ConsumerKeyWasHere&oauth_nonce=oauthNonceW