On 17 December 2010 13:26, Guo Yangguang <[email protected]> wrote: > [...] > I am developing an app for facebook.Facebook need to authorize the user > using the fllowing authorize url whose response should be a popup > iframe. > > #sorry,i can not post my client_id.this url with params is offered by > facebook,and i should replace the client_id and redirect_uri with myown. > > authorize_url="https://graph.facebook.com/oauth/authorize?client_id=...&redirect_ur=http://custom-survey.heroku.com/users/normal_auth_result"; > > #when user is not authorized,redirect to authorize_url to authorize user > #in my rails app. > > redirect_to(authorize_url) > > so when redirect_to(authorize_url) runs,a popup(2.png) should appear,but > i get an image with bottom link(1.png). what's more,when i click the > 1.png,the 2.png appears.I mean i should get the 2.png directly,not the > indirect one like above.I am sure i am doing to the fb doc,and the > authorize_url is made as fb doc says. > I think maybe it is because i am using the new beta authorizing > mechanism which is still in development.or maybe rails method > redirect_to has special grammar when it comes to non rails url with > params.
What happens if you put the url directly into the browser window? What does the rails log show when it runs the redirect? Colin -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en.
