A 401 often indicates a poorly-formed signature. I would take the
output of your JavaScript request and compare it visually with the
output of a good reference implementation, like Abraham's lib.
Sometimes it's hard to predict exactly what your output will look like
when trying to port across platforms/languages, even if the logic
appears correct.

Also, consider taking a dependency on a known good reference JS
implementation, like the one found on Google Code:


∞ Andy Badera
∞ +1 518-641-1280 Google Voice
∞ This email is: [ ] bloggable [x] ask first [ ] private
∞ Google me: http://www.google.com/search?q=andrew%20badera

On Thu, Feb 18, 2010 at 7:59 PM, Fernando Jorge <f.j.mot...@gmail.com> wrote:
> Hello, my name is Fernando, I am a Brazilian and developed a
> 'TwitterLib' JavaScript to be able to manage all the power of
> Twitter.Eu used the OAuth login to perform (and to show the extension
> name as the "From" in a tweet: D), but I have a problem in getting the
> Access Token, or better explained, Twitter me returns "401 Forbidden".
> I checked every line of code and found absolutely nothing that could
> damage, having considered until the code of Abraham's done in PHP Lib
> OAuth.The code function that captures the "access_token" and makes the
> request is available on PasteBin: http://pastebin.com/m7f4aa5c5 note
> that the same code is in JavaScript, because that I need help in that
> essentially no parte.Se find any fault, please return me and I can
> pass the functions performed by this function.
> Dwell (forward) returns.
> Detail: The Request Token is normally captured for information of all.

Reply via email to