Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
When building a Facebook tab application the first page receives the signed request, my question is what is the best practice to handle the secondary requests. You could save the related information in a cookie to have it on the secondary requests but that seems a little unsecured to me.
I am just curious what is the recommend way to handle this basic situation.
The signed request is just an intermediate step to getting the access_token and userid.
I put the access token into Session, and I also encrypt it and save it in a cookie. Facebook app development has taught me to go belt-and-suspenders when it comes to authentication.