Hi Taylor,
In order to test your 1st suggestion do you know if your HTTP
transport method munges any HTTP headers or adds its own HTTP headers
in any way? we created a simple test procedure on our public web
server, to simulate the google end point
https://api.twitter.com/oauth/access_token.
So
Hi Taylor,
In releatio to the 2nd test, I have used the values from
http://dev.twitter.com/pages/xauth and inserted these into my program
to step through the process.
Base string:
POSThttps%3A%2F%2Fapi.twitter.com%2Foauth
%2Faccess_tokenoauth_consumer_key%3DJvyS7DO2qd6NNTsXJ4E7zA
Hi Taylor,
Success, the missing peice of the puzzle was that we needed to send
the post Body, which although it was explained in documentation, we
thought it was there for explanation of how the values are accumulated
for the base string.. seems obvious now, but when your trying to do
this for
Hi Taylor,
Now I have the Access Token and I use the explanations in
http://dev.twitter.com/pages/auth to make a request on users behalf, I
get a response from twitter:
Twitter Response= {errors:[{code:53,message:Basic
authentication is not supported}]}
Status= 401
StatusTxt= Unauthorized
I am
Hi Martin,
Thanks for your patience in working through xAuth with the issues you're
facing. Given the information you've provided, it's difficult to determine
exactly what might be amiss here.
I'm unfamiliar with the programming environment you are using -- do you know
if your HTTP transport
We had an application successfully talking to twitter for a few years
prior to oAuth, and now converting this application to xAuth and cant
get past the first step.
The application gets a 401 Unauthorized response when attempting to
get the access token.
Have confirmed our program when provided
