Tab page applications tend to only send signed_request when making the first request, which makes the FacebookAuthorizeFilter to behave in undesirable ways when making future requests, since it's expecting a signed_request to be available.<br /><br />I fixed this in my app by extending the FacebookAuthorizeFilter and persisting the singed_request after it was parsed and validated in Session, and adding it when no signed_request OR parsed_signed_request are found to HttpContext.Items -not sure how the best approach to fixing this issue would be though-<br /><br />I'm looking forward to seeing this issue fixed in future releases so i could keep using this awesome addition to the framework in making facebook apps<br /><br />Thanks.
↧