I am away from my work computer so i cant try out this suggestion just yet but is this what it should look like when i do?
basestring: POST&http%3A%2F%2Fapi.twitter.com%2F1%2Fstatuses%2Fupdate.xml& oauth_consumer_key%3D3RmYCDlNEUoRLXmeQDgA%26 oauth_nonce%3D4E444934514E7A30544D344D6B3D673D%26 oauth_signature_method%3DHMAC-SHA1%26 oauth_timestamp%3D1284487942%26 oauth_token%3D180440869%2D38LrgS7ccUZ9l2M1SD5ODKclih3AOiUb6nist1y4%26 oauth_version%3D1.0%26 status%3Dsetting%2520up%2520my%2520twitter POST: POST /1/statuses/update.xml? HTTP/1.1 Content-Type: application/x-www-form-urlencoded Authorization: OAuth oauth_nonce="4E444934514E7A30544D344D6B3D673D", oauth_signature_method="HMAC-SHA1", oauth_timestamp="1284487942", oauth_consumer_key="3RmYCDlNEUoRLXmeQDgA", oauth_token="180440869%252D38LrgS7ccUZ9l2M1SD5ODKclih3AOiUb6nist1y4", oauth_signature="w8K2sgFoGQuF7NrMTEeoDtiOCYI%3D", oauth_version="1.0" Content-Length: 40 status=setting%20up%20my%20twitter On Sep 14, 2:18 pm, Taylor Singletary <taylorsinglet...@twitter.com> wrote: > MTCoder: > > You've got a little bit of an escaping problem here.. > > First, "spaces" aren't valid characters for your POST body. Personally, I > recommend using %20 to represent a space. "+" would also be valid in a POST > body. > > Once your POST body is correct, the escaping for your OAuth signature base > string is then considered. > > If you used %20 to encode spaces in your POST body, then in your signature > base string, %2520 should be used where a %20 was before. If you used "+" in > your POST body, %2B should be used instead of "+" in your OAuth signature > base string. > > The OAuth signature base string's validity depends on the initial, valid > encoding of your POST body. > > Taylor > > > > On Tue, Sep 14, 2010 at 1:11 PM, MTCoder <sguerr...@gmail.com> wrote: > > all the keys are the same that use when making calls to get the > > timeline. > > > Steve > > > On Sep 14, 1:08 pm, Tom van der Woerdt <i...@tvdw.eu> wrote: > > > Your Base String looks fine. Are you using the right keys to sign the > > > request? Is there any response from the API, except for 401? (Error > > > message?) > > > > Tom > > > > On 9/14/10 8:14 PM, MTCoder wrote: > > > > > still getting the 401 > > > > > basestring: > > > > POST&http%3A%2F%2Fapi.twitter.com%2F1%2Fstatuses%2Fupdate.xml& > > > > oauth_consumer_key%3D3RmYCDlNEUoRLXmeQDgA%26 > > > > oauth_nonce%3D4E444934514E7A30544D344D6B3D673D%26 > > > > oauth_signature_method%3DHMAC-SHA1%26 > > > > oauth_timestamp%3D1284487942%26 > > > > oauth_token%3D180440869%2D38LrgS7ccUZ9l2M1SD5ODKclih3AOiUb6nist1y4%26 > > > > oauth_version%3D1.0%26 > > > > status%3Dsetting%2520up%2520my%2520twitter > > > > > POST: > > > > POST /1/statuses/update.xml? HTTP/1.1 > > > > Content-Type: application/x-www-form-urlencoded > > > > Authorization: OAuth oauth_nonce="4E444934514E7A30544D344D6B3D673D", > > > > oauth_signature_method="HMAC-SHA1", oauth_timestamp="1284487942", > > > > oauth_consumer_key="3RmYCDlNEUoRLXmeQDgA", > > > > oauth_token="180440869%252D38LrgS7ccUZ9l2M1SD5ODKclih3AOiUb6nist1y4", > > > > oauth_signature="w8K2sgFoGQuF7NrMTEeoDtiOCYI%3D", oauth_version="1.0" > > > > Content-Length: 40 > > > > > status=setting%2520up%2520my%2520twitter > > > > > On Sep 14, 11:39 am, Tom van der Woerdt <i...@tvdw.eu> wrote: > > > >> It says "setting up my twitter" in the Base String, not > > "status=setting > > > >> up my twitter". > > > > >> Tom > > > > >> On 9/14/10 7:30 PM, MTCoder wrote: > > > > >>> Im posting this again here to make sure its seen (other thread here > > >http://groups.google.com/group/twitter-development-talk/browse_thread...) > > > > >>> I have tried many different things and cant seem to get the status > > > >>> POST to work(thanks Tom for the help with getting the timeline). > > > > >>> my base string: > > > > >>> POST&http%3A%2F%2Fapi.twitter.com%2F1%2Fstatuses%2Fupdate.xml& > > > >>> oauth_consumer_key%3D3RmYCDlNEUoRLXmeQDgA%26 > > > >>> oauth_nonce%3D544D44594D4E347A7735514D3D3D4934%26 > > > >>> oauth_signature_method%3DHMAC-SHA1%26 > > > >>> oauth_timestamp%3D1284483693%26 > > > >>> oauth_token%3D180440869%2D38LrgS7ccUZ9l2M1SD5ODKclih3AOiUb6nist1y4%26 > > > >>> oauth_version%3D1.0%26setting%2520up%2520my%2520twitter > > > > >>> And the POST: > > > > >>> POST /1/statuses/update.xml? HTTP/1.1 > > > >>> Content-Type: application/x-www-form-urlencoded > > > >>> Authorization: OAuth oauth_nonce="544D44594D4E347A7735514D3D3D4934", > > > >>> oauth_signature_method="HMAC-SHA1", oauth_timestamp="1284483693", > > > >>> oauth_consumer_key="3RmYCDlNEUoRLXmeQDgA", > > > >>> oauth_token="180440869%252D38LrgS7ccUZ9l2M1SD5ODKclih3AOiUb6nist1y4", > > > >>> oauth_signature="vZt0cwQJV%2FeZUPSRPAjfpEBhONM%3D", > > > >>> oauth_version="1.0" > > > >>> Content-Length: 40 > > > > >>> status=setting%2520up%2520my%2520twitter > > > > >>> Any help/ideas would be greatly appreciated. > > > > >>> Thanks > > > -- > > Twitter developer documentation and resources:http://dev.twitter.com/doc > > API updates via Twitter:http://twitter.com/twitterapi > > Issues/Enhancements Tracker: > >http://code.google.com/p/twitter-api/issues/list > > Change your membership to this group: > >http://groups.google.com/group/twitter-development-talk?hl=en -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk?hl=en
