Thank You... Thank You!!!
A third variable... nowhere in the online examples and no where in the
documentation!
WildCat you saved me from insanity!
On Sep 17, 7:35 pm, wildcat webmasterm...@gmail.com wrote:
Did you get this answered? If not, the answer is that Twitter returns
a URL variable
Did you get this answered? If not, the answer is that Twitter returns
a URL variable called OATH_VERIFIER that you need to add as the third
parameter in your getOAuthAccessToken request.
RLS
On Sep 14, 3:47 pm, Andy Reid andyreid...@gmail.com wrote:
Oddly enough. No. I just dumped the response
Oddly enough. No. I just dumped the response toString():
OAuthToken{token='z', tokenSecret='y',
secretKeySpec=null}
This is odd because it actually comes back to the correct page.
However, when I manually set the default callback url (in
dev.twitter.com) the oAuth worked
Sounds like the oauth_callback parameter for /oauth/request_token is
wrong. ;-)
Tom
On 9/14/10 10:47 PM, Andy Reid wrote:
Oddly enough. No. I just dumped the response toString():
OAuthToken{token='z', tokenSecret='y',
secretKeySpec=null}
This is odd because it actually
