It's working now. I changed the method for url encoding my post variables and that seemed to fix the problem. I'm using the UrlEncode method from the .NET oAuth library instead of HttpUtility's method.
On Mar 19, 2:40 pm, Shannon Whitley <[email protected]> wrote: > I'm running into this as well. My POSTs are not working (401 error). > GETs are fine. > > On Feb 16, 11:50 pm, Ryan W <[email protected]> wrote: > > > 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,ChadEtzel<[email protected]> wrote: > > > > I have gottenOAuthGET requests working nicely, but POST is a > > > different story. I am trying to post an update (tweet) usingOAuth, > > > 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 "InvalidOAuthRequest" 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 "InvalidOAuthRequest" > > > 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
