I've been using the referrer to capture callback data. You might want to try that.
On May 1, 2:29 pm, Jesse Stay <jesses...@gmail.com> wrote: > Thanks Matt. I'll try to handle it in my session for now. BTW, I think > I've finally got Perl working - will be doing a post and transferring over > to the wiki as soon as I feel comfortable with it. > Jesse > > > > On Fri, May 1, 2009 at 3:12 PM, Matt Sanford <m...@twitter.com> wrote: > > > Hi Jesse, > > > This was available with the oauth_callback parameter but it had to be > > removed for security reasons. I'm currently working with the OAuth group to > > finalize a way to bring oauth_callback back. I have some working code based > > on the current discussion but we're still hashing some things out before it > > will be ready. Hopefully we'll be able to bring it back soon. I'll post and > > update to the list once I have something ready. > > > Thanks; > > – Matt Sanford / @mzsanford > > Twitter Dev > > > On May 1, 2009, at 2:09 PM, Jesse Stay wrote: > > > Forgive my OAuth n00bness, but I was curious if there was a way to pass > >> parameters that will in return get passed back to my callback URL in OAuth. > >> For instance, I want to pass the parameters, and then when Twitter > >> redirects back to my callback URL I want it to also pass the additional > >> parameters so I can do different things with the same callback URL > >> depending > >> on what I'm trying to do with OAuth at the time. > > >> Is this possible? And how? > > >> Thanks, > > >> @Jesse- Hide quoted text - > > - Show quoted text -
