On 17 December 2010 15:03, Guo Yangguang <[email protected]> wrote: > Colin Law wrote in post #969060: >> On 17 December 2010 13:26, Guo Yangguang <[email protected]> wrote: >>> #when user is not authorized,redirect to authorize_url to authorize user >>> 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? >> when put it in browser directly,the response works well like fb doc > says,popuping an iframe. > >> What does the rails log show when it runs the redirect? >> i have attached the server log images.As it shows,when 'signed_request' param > implys the user is not authorized in the home/index method,he will be > redirected > to fb url(whose response should be popup window) > "https://graph.facebook.com/oauth/authorize?client_id=...&redirect_uri=http://custom-survey.heroku.com/users/normal_auth_result".But > i still need to click 1.png to get popup window.
So you are saying that if you enter the url directly in the browser you get one result, but if you use rails to redirect to exactly the same url then you get a different effect? What happens if you just put a link to that url on your web page and click it? 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.
