Note that there are some explanatory texts on larger screens.

plurals
  1. POI have to make public URLs for private actions?
    primarykey
    data
    text
    <p>Lets say I have a website where I allow users to perform actions (communicate, post photos, etc) on their friends on my site (they are friends on Facebook). This is private information between User A and User B.</p> <p>Before the new Open Graph [beta] I would encode as much information as needed in the original <code>POST</code> request. But now Facebook has moved to a more "callback" scheme where I do a simple <code>POST</code> and provide a URL which FB then hits via <code>GET</code> and I provide series of <code>og:</code> tags to describe the core content - all of this is the information that I would have PREVIOUSLY provided in the first and only <code>POST</code> request.</p> <p>Here in lies the problem though: I have to provide a completely un-authenticated URL for FB to hit (the <code>GET</code>) and it has to be the same URL the app will use in the Timeline, so I cannot make a special, secure by obscurity URL as the callback, but provide a "friendly" URL (which would require authentication) to be used as the click through URL in the timeline.</p> <p>Am I understanding this correctly?</p> <p>EDIT: this would also be a different issue if FB when doing the callback <code>GET</code> would provide some kind of authentication data in the URL or HTTP headers, but after examining the complete HTTP details in the <code>GET</code> request FB is giving us nothing other than a special <code>User-Agent</code> that we can use to differentiate the request.</p> <p>UPDATE: I believe this question is driving at the same issue. IF we can provide a different <code>og:url</code> on our gibberish "callback" page then it would make things a lot easier.</p> <p><a href="http://facebook.stackoverflow.com/questions/7561071/can-you-have-your-opengraph-object-link-to-a-different-url">Can You Have Your OpenGraph Object Link to a Different URL?</a></p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload