=87aaa10a26a77fb99837fe711ecbaaa5;topic=38.msg43
On Nov 2, 11:22 pm, Martin Hannah mhan...@coresoft.com.au wrote:
Hi Taylor,
Now I have the Access Token and I use the explanations
inhttp://dev.twitter.com/pages/authto make a request on users behalf, I
get a response from twitter:
Twitter
Hi Taylor: For your interest (In case someone else asks):
We now have oAuth/xAuth working for Progress open edge and have the
basic Twitter status and command functions operational as they were
before. There is sample source and Progress open edge twitter
libraries we are working on now at
the entire HTTP request, including headers sent/received, the raw POST
body, etc -- which may yield an obvious answer as to why your implementation
is not working.
Hang in there!
Taylor
On Tue, Oct 26, 2010 at 3:20 PM, Martin Hannah mhan...@coresoft.com.auwrote:
We had an application
is not working.
Hang in there!
Taylor
On Tue, Oct 26, 2010 at 3:20 PM, Martin Hannah mhan...@coresoft.com.auwrote:
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
this for 1st time, it wasnt obvious then.
So the find part of the send is:
objHTTP:send(x_auth_username=oauth_test_execx_auth_password=twitter-
xauthx_auth_mode=client_auth).
So my last question is, should this be url encoded, because when we
URL encoded (as the doco suggests) it did NOT work.
Martin Hannah
=1.0, status=PostingthroughMicrosoftXMLHTTP
Any suggestions ?
Martin Hannah wrote:
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
, Martin Hannah mhan...@coresoft.com.au wrote:
Hi Matt,
Thanks for the response, I went back and looked closely at the
possible trouble spots you suggested (the epoch time, the consumer
key, the parameters not repeated) and its all fine.
I used the program to produce epoc time and compared
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
/xauth .?
Can anyone help ..?
On Oct 24, 9:55 am, Martin Hannah mhan...@coresoft.com.au wrote:
Hi Matt,
Thanks for the response, I went back and looked closely at the
possible trouble spots you suggested (the epoch time, the consumer
key, the parameters not repeated) and its all fine.
I used
or POST parameters.
Best
@themattharris
Developer Advocate, Twitter
http://twitter.com/themattharris
On Wed, Oct 6, 2010 at 4:37 PM, Martin Hannah mhan...@coresoft.com.au wrote:
We are converting our Twitter interfaces to oAuth and from the advise
on http://twittervb.codeplex.com
We are converting our Twitter interfaces to oAuth and from the advise
on http://twittervb.codeplex.com/wikipage?title=XAuth we are heading
down the path of xAuth for our desk top applications that use Twitter.
We opted not to use TwitterVB.dll for backward compatibility of older
sites, so we are
11 matches
Mail list logo
