Isn't that using a GET request versus the docs saying POST? And I
thought parameters were supposed to be normalized except for signature
which gets attached at the end?
On Mar 2, 3:40 pm, Marc Mims <marc.m...@gmail.com> wrote:
> * Berto <mstbe...@gmail.com> [100302 13:28]:
> > At first I thought this might be because HttpURLConnection wasn't
> > handling SSL, but then I switched over to HttpPost (this code is in
> > Java) which I know will handle SSL and I'm still getting a 401. I'm
> > doing everything the same as with oauth, except passing the request
> > token (I'm not even getting a request token any more) and I'm passing
> > the x_auth_* parameters as regular parameters in the POST body. The
> > three x_auth_* parameters are my only parameters and the normal OAuth
> > header is in the "Authorization" field. I'm POSTing to the new access
> > URL as specified in the xAuth docs with no success .
> > Thoughts anyone? I feel like such a noob asking for so much help with
> > oAuth/xAuth :\.
> I have successfully implemented xAuth in the Perl Net::Twitter library.
> Here's what a Net::Twitter generated xAuth request looks like:
> User-Agent: Net::Twitter/3.11008 (Perl)
> X-Twitter-Client: Perl Net::Twitter
> X-Twitter-Client-Version: 3.11008
> For this example, I used:
> consumer_key = 'CONSUMER_KEY'
> consumer_secret = 'CONSUMER_SECRET'
> x_auth_username = 'fred'
> x_auth_secret = 'secret'
> Hope this helps.