[twitter-dev] Re: xAuth request returns 401, need help

[Eric Will]

Was the cause of the empty response body ever discovered?  I'm having
a similar issue, except my 401 response body has "Content-Length: 1"
containing an empty space " ".


On Nov 19 2010, 3:44 pm, Matt Harris 
wrote:
> Hey Chrys,
>
> Agreed. The authentication header doesn't have to be in order but as said
> previously, it helps with debugging.
>
> It is really strange that the response body is empty. It maybe easier if you
> email me the full request headers, with response headers and content so I
> can debug further. For security it'll be easier if you email me that
> directly.
>
> Best,
> @themattharris
> Developer Advocate, Twitterhttp://twitter.com/themattharris
>
>
>
>
>
>
>
> On Fri, Nov 19, 2010 at 12:20 PM, Chrys Bader  wrote:
> > Also, the example here shows that the Auth header and the base string
> > aren't in the same order:
>
> >http://dev.twitter.com/pages/xauth
>
> > On Nov 19, 11:04 am, Matt Harris  wrote:
> > > Hey Chrys,
>
> > > The order of the parameters in the base string matter and they should be
> > in
> > > lexicollexicographical order. For ease of debugging and to remove any
> > > ambiguity it would be better to have the authorization header use the
> > same
> > > order too.
>
> > > Can you tell me what the body content of the 401 error is?
>
> > > Best,
> > > @themattharris
> > > Developer Advocate, Twitterhttp://twitter.com/themattharris
>
> > > On Thu, Nov 18, 2010 at 6:55 PM, Chrys Bader  wrote:
> > > > Does the order of the params in either the Authorization or Base
> > > > string matter?
>
> > > > Here are my Request Headers:
>
> > > >    Authorization = "OAuth oauth_timestamp=\"1290134876\", oauth_nonce=
> > > > \"D3EC42D2-A37F-4298-987D-0F9603B0C9C7\", oauth_version=\"1.0\",
> > > > oauth_consumer_key=\"xxx\", oauth_signature_method=\"HMAC-SHA1\",
> > > > oauth_signature=\"MOWT%2BaSs35RhzvRRMVxRG0Y5p0E%3D\"";
> > > >    "Content-Length" = 71;
> > > >     "Content-Type" = "application/x-www-form-urlencoded;
> > > > charset=utf-8";
>
> > > > Here is my actual base string:
>
> > > > POST&https%3A%2F%2Fapi.twitter.com%2Foauth
> > > > %2Faccess_token&oauth_consumer_key%3Dxxx%26oauth_nonce%3DD3EC42D2-
> > > > A37F-4298-987D-0F9603B0C9C7%26oauth_signature_method%3DHMAC-
> > > > SHA1%26oauth_timestamp%3D1290134876%26oauth_version%3D1.0%26x_auth_mode
> > > > %3Dclient_auth%26x_auth_password%3Dxxx%26x_auth_username%3Dchrysb
>
> > > > On Nov 18, 6:47 pm, Chrys Bader  wrote:
> > > > > Yes I compared the UTC timestamp that my phone is generating with the
> > > > > actual UTC timestamp, and they were the same.
>
> > > > > Is there anything else I can show you for more information?
>
> > > > > No matter what, I just keep getting a 401 response from Twitter.
>
> > > > > On Nov 18, 6:41 pm, Matt Harris  wrote:
>
> > > > > > OK, but is the UTC timestamp actually accurate? we've heard of a
> > number
> > > > of
> > > > > > phones whose date/time are wildly wrong. It maybe find but it's
> > quite
> > > > > > common.
>
> > > > > > Your content-type is fine.
> > > > > > Matt
>
> > > > > > On Thu, Nov 18, 2010 at 6:03 PM, Chrys Bader 
> > wrote:
> > > > > > > Ok, I looked into it.  According to the iPhone SDK documentation,
> > I
> > > > am
> > > > > > > indeed sending the UTC (GMT) timestamp.
>
> > > > > > > Still not sure what else could be wrong?
>
> > > > > > > Is this the right Content-Type?
>
> > > > > > > "Content-Type" = "application/x-www-form-urlencoded;
> > charset=utf-8";
>
> > > > > > > On Nov 18, 5:53 pm, themattharris 
> > wrote:
> > > > > > > > Hey Chrys,
>
> > > > > > > > A couple of things to check first:
>
> > > > > > > > 1. Have you been granted xAuth access?
> > > > > > > > 2. Double check the timestamp of your request is within 10 or
> > so
> > > > > > > > minutes of the time returned by Twitter's servers. Our server
> > time
> > > > is
> > > > > > > > in UTC.
> > > > > > > > 3. Verify your encoding is correct. For example: a password
> > like
> > > > ab$
> > > > > > > > %&123 should be in your basestring as ab%2524%2525%2526123 and
> > in
> > > > your
> > > > > > > > post body as ab%24%25%26123.
>
> > > > > > > > Best,
> > > > > > > > Matt
>
> > > > > > > > On Nov 18, 5:31 pm, Chrys Bader  wrote:
>
> > > > > > > > > *bump*
>
> > > > > > > > > I've run my base string through an oAuth verifier (
> > > >http://quonos.nl/
> > > > > > > > > oauthTester/), and it all checks out!
>
> > > > > > > > > Any ideas?
>
> > > > > > > > > On Oct 27, 4:50 pm, Chrys Bader  wrote:
>
> > > > > > > > > > Hey all,
>
> > > > > > > > > > This is my first post in this group, hi!
>
> > > > > > > > > > I am having trouble making a request onhttps://
> > > > > > > api.twitter.com/oauth/access_token.
> > > > > > > > > > I've been at this for 2 days and I can't make any progress.
> >  I
> > > > feel
> > > > > > > > > > like everything matches up with all examples,
> > documentation,
> > > > and
> > > > > > > other
> > > > > > > > > > forum posts perfectly.
>
> > > > > > > > > > Here is my post body:
>

[twitter-dev] Re: xAuth Approval

[Iman Zarrabian]

cool thanks ;)
I just wrote you back with all the details

Iman

On 15 déc, 19:51, Brian Sutorius  wrote:
> We attempt to respond to these requests within a couple business days.
> I just located your ticket and will follow up now.
>
> Brian Sutorius
>
> On Dec 15, 4:53 am, Iman Zarrabian  wrote:
>
>
>
> > Hi all, I'm new to the whole OAuth/xAuth thing 
> > I'd like t know how long it's gonna take to twitter api team to
> > authorize a xAuth use request ? any feedback on that ? I guess you got
> > this question 100 times a day, no ? sorry ;)
>
> > thx in advance

-- 
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
http://groups.google.com/group/twitter-development-talk

[twitter-dev] Re: xAuth Approval

[Brian Sutorius]

We attempt to respond to these requests within a couple business days.
I just located your ticket and will follow up now.

Brian Sutorius

On Dec 15, 4:53 am, Iman Zarrabian  wrote:
> Hi all, I'm new to the whole OAuth/xAuth thing 
> I'd like t know how long it's gonna take to twitter api team to
> authorize a xAuth use request ? any feedback on that ? I guess you got
> this question 100 times a day, no ? sorry ;)
>
> thx in advance

-- 
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
http://groups.google.com/group/twitter-development-talk

[twitter-dev] Re: Xauth 401 error....T^T by iOS

[Bess]

Your xAuth is not approved and activated yet - 401 error

On Dec 12, 6:59 pm, Mchello  wrote:
> I use this source athttps://github.com/aral/XAuthTwitterEngine
>
> first..
>
> I register my App at dev.twitter.com
>
> and send message to a...@twitter.com .. about Xauth Key..
>
> and i get consumerKey and consumerSecret..
>
> I change consumerKey and consumerSecret line at XauthTwitterEngine
>
> I can get tokenString
>
> but.. i send twit message..
>
> i get 401 error..
>
> my id and password not wrong..
>
> everybody success use this source.. but i can't
>
> please send to me .. why 401 error..
>
> if you want my consumerKey and Secret .. I can..
>
> mche...@me.com <== please ..

-- 
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
http://groups.google.com/group/twitter-development-talk

Re: [twitter-dev] Re: xAuth Request gives Error from samsung tv maple browser

[umamahesh G.]

HI Tom

Thank you very much for Your kind Support.Still i could not able to get
Response from Twitter from firefox and samsung TV app.
But it is working in Safari.Here i am sending the clean  code as an
attachment please help me out where the hurdle exist.
If you make it work in firefox surely works in samsung TV. So please help me
Tom.
Thanks.

On Tue, Dec 7, 2010 at 3:52 PM, Tom van der Woerdt  wrote:

> That code is really a mess, but I think I found a few issues and solved
> them. I'm not sure about the Signature itself, but the Base String is fine
> now.
>
> I've attached a "new" version of your .html file. I won't paste the code
> here because it may "break" the code.
>
> Tom
>
> PS: I really recommend keeping your code clean. This file is a mess.
>
>
>
>
> On 12/7/10 6:07 AM, umamahesh G. wrote:
>
>> HI Tom,
>>
>> Thanks for you kind support.I had all required privileges from twitter
>> for my app.The thing is i can able to post the message from safari but
>> same code not working in firefox,IE as well as samsung Tv.Please help me
>> out from this problem.I tried maximum ways still i don't have any
>> solution.
>>
>> On Tue, Dec 7, 2010 at 5:48 AM, Bess > > wrote:
>>
>>I am interested in solving this too.
>>
>>Let's say Samsung TV is same as desk top. You should be able to use
>>xAuth.
>>
>>You need to create a new Twitter app to get Consumer key and Consumer
>>secret. Make sure you select client method and read/write.
>>
>>On Dec 6, 1:23 am, "umamahesh G." > > wrote:
>> > HI Tom,
>> >
>> > Thanks for your support. I am using javascript for samsung TV
>>Applicaiton
>> > not for normal browser so there is no way to know about keys and
>>secret
>> > key.Actually Samsung SDK uses Maple browser and  application runs
>>on  this
>> > browser.
>> >
>> > I hope you help me out from this issue.
>> >
>> > Please find the below code.
>> >
>> > 
>> > 
>> >