Here's the string. The forum turned it into a link. oauth_consumer_key=XXXXXXXXXXXXXXXXXXXXXX&oauth_nonce=72BF80D5959F5A35DA5F8748AE8DBA151015DC4C&oauth_signature=Hje29X769TqIF %2B1CaJkr1i5BIVo%3D&oauth_signature_method=HMAC- SHA1&oauth_timestamp=1237485161&oauth_version=1.0&oauth_token=14846470- H7Wh5o8atU93C7MSwmzYi3IFd1JXPIq2rx2IzSVxc&oauth_token_secret=MGNcSBAQFj8vCGhyY9hmiIpvuIIn082ChJWOSJ8II
On Mar 19, 1:33 pm, rlamfink <[email protected]> wrote: > Oauth noob. I've got all the token exchange parts working and can get > an access_token& secret. But when I make an http POST, the captured > url string looks right, but I get Invalid Oauth Request with a status > code of 401. > > Here's the string with the security sensitive parts changed. > Is there something obvious that I'm missing? > > http://twitter.com/statuses/update.xml?oauth_consumer_key=XXXXXXXXXXX...
