I am trying to create a simple "Log in with twitter application".
I am using this example: http://www.voiceoftech.com/swhitley/?p=681.
You can get all the code there.

But it throws out an error at this line

Response.Redirect(oAuth.AuthorizationLinkGet()); in oAuthTwitter
WebResponseGet.

Thanks for your help.

Sincerely, Jure


On 9 avg., 16:53, Taylor Singletary <taylorsinglet...@twitter.com>
wrote:
> xAuth would not require this as no callback is utilized. In the case of
> actually executing API resource actions (like sending a tweet), your
> callback (and effectively OAuth itself) has nothing to do with the request
> -- it's only a means of identifying the two parties involved in the request
> ("the user" and "the application").
>
> On Mon, Aug 9, 2010 at 7:51 AM, Andrew W. Donoho 
> <andrew.don...@gmail.com>wrote:
>
>
>
>
>
> > On Aug 9, 2010, at 08:37 , Taylor Singletary wrote:
>
> > > As a reminder, it's proper OAuth to always send an oauth_callback on the
> > request token step of OAuth negotiation -- even if you've preregistered a
> > callback or are using the PIN code/out-of-band flow (in which case you would
> > send oauth_callback=oob).
>
> > Taylor,
>
> >        As a user of xauth, I do  not currently send "oauth_callback=oob". I
> > think this is because xauth does not participate in the negotiation for a
> > temporary credential. (See: <http://tools.ietf.org/html/rfc5849> section
> > 2.1.). Is this your understanding? Or do xauth users need to include this
> > callback in our request for our permanent access token?
>
> > Anon,
> > Andrew
> > ____________________________________
> > Andrew W. Donoho
> > Donoho Design Group, L.L.C.
> > a...@ddg.com, +1 (512) 750-7596
>
> > "We did not come to fear the future.
> >    We came here to shape it."
>
> > -- President Barack Obama, Sept. 2009

Reply via email to