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 luiz.felipe...@gmail.com wrote:
Hi,
since a few days ago, my status
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 duane.roela...@gmail.com wrote:
And please forgive my obnoxious tone; I'm tired and frustrated. :)
On Feb 4, 12:05 am, Duane Roelands
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 ryanalford...@gmail.com 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
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
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
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 duane.roela...@gmail.comwrote:
I ended up rolling back my library
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
And please forgive my obnoxious tone; I'm tired and frustrated. :)
On Feb 4, 12:05 am, Duane Roelands duane.roela...@gmail.com 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
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,
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:
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
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
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 arian.cabe...@gmail.com wrote:
Hi Ryan.
I´m having the same problem with the statuses/update using the php
library provided by Twitter, name as :
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
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
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-6BB80EF9B45Boauth_signature_method=HMAC-
SHA1oauth_timestamp=1264527609oauth_token=9353572-
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:
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?
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 bac...@gmail.com 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
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 ryanalford...@gmail.comwrote:
Don't do the POST request data. You
Also noticed, minor thing, but your signature ends in '%253d'
Mine in uppercase '%253D'
The hash algorithm can product both upper and lower case letters..
Ryan
On Tue, Jan 26, 2010 at 1:53 PM, eco_bach bac...@gmail.com wrote:
Also noticed, minor thing, but your signature ends in '%253d'
Mine in uppercase '%253D'
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.
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 bac...@gmail.com wrote:
Hi Ryan
Changed to 'GET' and it seems I still get the Incorrect
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
25 matches
Mail list logo
