I'm taking a standalone Restlet web app that I've built and porting it to
Facebook. One integration option is where you put your app in an iframe.
They then call your server at the specified URL, tacking on a ton of
parameters.
So if I have it up at myapp.example.com, their call would start off with
http://myapp.example.com/?fb_sig_in_iframe=1&fb_sig_time=1203726811.1843
and go on from there for about half a block. From my purpose, the
interesting part is the bit about authentication.
To my initial surprise, the Router doesn't route that to my restlet at
"/". Looking at the Router and Route source, it is trying to route on the
whole URL, all the params included. But thinking further, that makes
sense: the Router is expecting RESTful requests, not ones like this. Is
that the right way to think of it?
If so, then it looks like I should either capture the request right away
and rewrite it or capture the facebook handshake and redirect to the
proper URL. Does that make sense? Or are there better approaches for
handling not-so-restful GETs?
Thanks,
William
