Since it's GET works and POST, no. 1 reason is to make sure the base URI in the base signature string is constructed correctly. In your example, you don't need source=xxxx since it's OAuth.
-- Hwee-Boon On Jun 6, 8:56 pm, rhysmeister <therhysmeis...@hotmail.com> wrote: > Hi All, > > I am having problems identifying what is wrong with converting my app > to use oAuth. All my GET requests work fine but my POST requests all > fail with an incorrect signature error. I am adding the oauth > parameters to the authorisation header of my request. My authorisation > header is build like below for GET requests (this works); > > OAuth > oauth_timestamp="1234567890",oauth_nonce="xxxxxx",oauth_version="1.0",oauth > _signature_method="HMAC- > SHA1",oauth_consumer_key="xxxxxx",oauth_token="xxxxxx",oauth_signature="xxx > xxx" > > My POST requests (these don't work); > > OAuth > oauth_timestamp="1234567890",oauth_nonce="xxxxxx",oauth_version="1.0",oauth > _signature_method="HMAC- > SHA1",oauth_consumer_key="xxxxxx",oauth_token="xxxxxx",oauth_signature="xxx > xxx" > > I get the below error returned... > > <pre> > <?xml version="1.0" encoding="UTF-8"?> > <hash> > <request>/1/statuses/update.xml?source=xxxxxxxxxx</request> > <error>Incorrect signature</error> > </hash> > > Would anyone be able to provide any pointers here? > > Cheers, > > Rhys
