oauth_callback and oob error

[Babak]

HI all,

I'm new at OAuth and every time I try to request for a token from
https://api.twitter.com/oauth/request_token

it returns me this error :
/oauth/request_token Desktop applications only support the
oauth_callback value 'oob'

I'm not developing a Desktop app !!!! its a Web application (JS app).

I used this library in my application:
http://oauth.googlecode.com/svn/code/javascript/

And the weird thing is that when I remove oauth_callback from post
parameters it returns the "true" value for "oauth_callback_confirmed"
like this :
oauth_token=XXXX&oauth_token_secret=XXXX&oauth_callback_confirmed=true

Any idea what am I doing wrong ?

[Tom van der Woerdt]

Is your application marked as a web app on http://dev.twitter.com/apps ?

Tom

[Babak]

Thanks Tom.

well, I choose the Browser as Application Type.

But I left the callback url field blank and it saved my settings
nicely ! and then when i checked it back the application type was
changed to client !!!!!!
and this time i wrote something in callback url field and seems it
really saved my settings.

so is it a bug in app settings page validation ?

[Matt Harris]

This is a known quirk of how that page works. If you don't provide a
callback URL we default you back to a client application. To be able
to have a browser based application the callback URL must be
specified. When doing this remember you should still send a
oauth_callback during the request_token phase of the OAuth flow.

Hope that helps,
Matt

> --
> 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?hl=en
>

--

Matt Harris
Developer Advocate, Twitter
http://twitter.com/themattharris

[Babak]

Thanks for reply.
Kindly id like to discuss about this with some inline comments.

On Sep 8, 4:30 am, Matt Harris <thematthar...@twitter.com> wrote:
> This is a known quirk of how that page works.

> If you don't provide a callback URL we default you back to a client application.

Without any notification ?!?!?

> To be able to have a browser based application the callback URL must be
> specified.

So your developers should implement this as a rule of validating that
form.