-enter
it type of message.
What is the *correct* behavior for a 401?
thx,
--dwf
--
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
=fail
err code=1001 msg= Invalid username or verification URL specified/
/rsp
There's one comment on their Google Group with someone else getting
this suddenly after having successful code for a while.
Thoughts?
--dwf
We're having lots of success with OAuth now, which is great. So far
it looks like all our GETs are working just fine. And some of our
POSTs - but not all.
Here's a POST that works (deleting a user's tweet):
url: https://api.twitter.com/1/statuses/destroy.json
parameters: {id: 12532480661}
Just tried removing the source param and we still get the 'incorrect
signature' error.
Twurl from the command line is just fine.
Digging further...
--dwf
On May 21, 11:54 am, Taylor Singletary taylorsinglet...@twitter.com
wrote:
Hi DWF,
AT first glance there doesn't seem to be anything
Hang on, we think we found somethingstop digging for a bit. :)
On May 21, 12:11 pm, DWF dwfr...@pivotallabs.com wrote:
Just tried removing the source param and we still get the 'incorrect
signature' error.
Twurl from the command line is just fine.
Digging further...
--dwf
On May 21
.
It appears the % character was confusing the server and so we kept
getting 401s.
Our solution is to make a simpler, non-Base64-encoded nonce. NO
PERCENTS!!! And all is now well.
-dwf
On May 12, 3:30 pm, DWF dwfr...@pivotallabs.com wrote:
Taylor: Here's what we're sending now. The signature looks
http://dev.twitter.com/doc/get/statuses/mentions
This API doesn't take a parameter for a username so it's only
available via an auth call.
We tried to hit http://api.twitter.com/1/statuses/mentions.json via
Hurl.it and got a 401.
Which means that the doc is wrong wrt auth URL.
--dwf
to validate oauth signature and token
This look familiar to anyone?
Thanks,
--dwf
We just coded up a simple Ruby script to make the same request,
building our post body by hand into a string to ensure the escaping
(or not) of the params.
So we know that going into Net::HTTP the underscores are underscores
and NOT %5F's.
Same response from the server.
--dwf
On May 12, 11
It turns out that we have a base64 encoding problem, which means our
signature actually is bad.
Working on it now.
--dwf
On May 12, 1:06 pm, DWF dwfr...@pivotallabs.com wrote:
We just coded up a simple Ruby script to make the same request,
building our post body by hand into a string
: Accept-Encoding
Connection: close
Failed to validate oauth signature and token
On May 12, 2:56 pm, DWF dwfr...@pivotallabs.com wrote:
It turns out that we have a base64 encoding problem, which means our
signature actually is bad.
Working on it now.
--dwf
On May 12, 1:06 pm, DWF
11 matches
Mail list logo
