Any luck with this? Running into the same problem here, wondering what the right combination of data to put in URL params vs post data vs headers, etc.
On Feb 14, 12:18 pm, Chad Etzel <[email protected]> wrote: > I have gotten OAuth GET requests working nicely, but POST is a > different story. I am trying to post an update (tweet) using OAuth, > and I'm not quite sure where to put all of the parameters. > > Endpoint:http://twitter.com/statuses/update.xml > > I have tried puting all of the parameters (status, source, > in_reply_to_id, oauth_*) in the POSTDATA fields of the request, but I > get a 401 "Invalid OAuth Request" response. > > Then I tried putting just the twitter specific params (status, source, > in_reply_to_id) in the POSTDATA fields, and leaving the oauth_* params > in the query string of the URL. Same 401 "Invalid OAuth Request" > response. > > I am curious which of these ways *should* work? > > I can get verify_credentials, favorites, etc using the same > oauth_token and nonce/signature methods just fine. > > Anybody got POST requests going yet? > > Thanks, > -Chad
