Matt, Try to register a new application for your development environment. I know it sounds not smart, but I guess it is a simple way to achieve. I think twitter did the same to me , when I tired to change the call back url.
regards R On Sun, Jul 26, 2009 at 1:50 PM, mattarnold1977 <matt.arnold.1...@gmail.com>wrote: > > Andy, > > That was it! Sorting my parameters did the trick. After that I was > able to successfully post a web request to Twitter's OAuth request > token URL. > > Now, the next problem. I'm working in a development environment and I > can not get the call back argument to work correctly. I've added it > as a parameter in my web request and you can see it in the URL when > logging into Twitter to get the token. But, Twitter just returns me > back to my application that I registered with them (not my development > environment that I've setup in my call back argument). > > -Matt > > On Jul 26, 4:55 am, Andrew Badera <and...@badera.us> wrote: > > On Sat, Jul 25, 2009 at 6:46 PM, mattarnold1977 > > <matt.arnold.1...@gmail.com>wrote: > > > > > > > > > Bojan, > > > > > Thanks for the reply. I'm using ASP .NET. > > > > > -Matt > > > > I suspect Bojan was more curious about what OAuth library you're using. > If > > you're doing it on your own, allow me to suggest DotNetOpenAuth instead. > > > > Also, are you sorting your parameters correctly? Non-alphabetized sort of > > parameters prior to signing will give you a 401. > > > > Thanks- > > - Andy Badera > > - and...@badera.us > > - Google me:http://www.google.com/search?q=andrew+badera > > - This email is: [ ] bloggable [x] ask first [ ] private >
