My signed request looks like this when viewing a non-authorized page.
Array (
[algorithm] => HMAC-SHA256
[issued_at] => 1328803958
[page] => Array (
[id] => 114951721840
[liked] => 1
[admin] => 1 )
[user] => Array (
[country] => us
[locale] => en_US
[age] => Array ( [min] => 21 )
)
)
After authorizing the app, the initial tab page signed request looks like this.
Array (
[algorithm] => HMAC-SHA256
[expires] => 1328810400
[issued_at] => 1328804617
[oauth_token] => AAAEQiWKOJTUBAB7la6TzNybfDkv6eYwtGUayappUspm3hWx6qKAFw3Ahbdhqv1xZC27WmrZC0yMMdtE0pdxoiUruZABg1zN1DalnYqS5AZDZD
[page] => Array (
[id] => 114951721840
[liked] => 1
[admin] => 1 )
[user] => Array (
[country] => us
[locale] => en_US
[age] => Array ( [min] => 21 )
)
)
[user_id] => 30811359
)
And finally, once I navigate away from this page, the signed request looks like this.
Array (
[algorithm] => HMAC-SHA256
[code] => 2.AQAq5nTl5j7tMkqF.3600.1328810400.5-30811359|tXdv-ci5z1GIzo9CY5HXp_piL3I
[issued_at] => 1328804621
[user_id] => 30811359
)
I can determine user likes with a valid user, but I want to figure out why I lose the standard signed request data after navigating from the initial tab page.
UPDATE : If I store the signed request into a session variable and load it on subsequent pages, I maintain the full signed request. Is there a reason I should not do this?