Just for kicks try a GET instead of a POST. On Sun, Mar 22, 2009 at 15:18, Jamie Rumbelow <ja...@jamierumbelow.net>wrote:
> > Can anyone give me a hand? > > Jamie Rumbelow Designer / Developer / Writer / Speaker > http://www.jamierumbelow.net | +44 (0)7956 363875 | jamie (at) > jamierumbelow > (dot) net > > -----Original Message----- > From: twitter-development-talk@googlegroups.com > [mailto:twitter-development-t...@googlegroups.com] On Behalf Of Cameron > Kaiser > Sent: 21 March 2009 20:27 > To: twitter-development-talk@googlegroups.com > Subject: [twitter-dev] Re: Invalid oAuth Request > > > > I'm having a little trouble with oAuth - I'm getting an Invalid OAuth > > Request with a HTTP 401. I'm sure the signature is correct, and all > > I'm trying to do is get a request token. Has anyone had this problem > > before and if so how did you fix it? > > Code and/or output is always helpful. > > -- > ------------------------------------ personal: > http://www.cameronkaiser.com/ > -- > Cameron Kaiser * Floodgap Systems * www.floodgap.com * > ckai...@floodgap.com > -- If there was a hole, I would jump into it. -- Gackt Camui > ------------------ > No virus found in this incoming message. > Checked by AVG - www.avg.com > Version: 8.0.238 / Virus Database: 270.11.20/2013 - Release Date: 03/20/09 > 19:01:00 > > -- Abraham Williams | http://the.hackerconundrum.com Web608 | Community Evangelist | http://web608.org This email is: [ ] blogable [x] ask first [ ] private. Sent from: Madison Wisconsin United States.
