tsa-r

The problem was malformed Json.

with this

I finally got it to work. Several issues existed. Not with the signatures and the authorization headers. Instead issues existed in the time stamp used, which was not synchronized properly and also not in GMT as twitter is expecting. I synchronized my system clock against time.google.com and this part was done. Now, there was also an issue about the header which needed also sorting, contrary to twitter's own docs talking about sorting in the context of the signature base string only. I found out that also the extended header needs sorting. Extended because it contains the tweet itself which is not part of the signature calculation. once this part was built in posting the tweet was successful

First of all you can change $output = curl_exec($ch); to echo $output = curl_exec($ch); .This way you will see error messages in your browser.

Also, try urlencode($url); in case your url has some white spaces in it.

But Your problem is most likely the security of the target server.Lots of servers treat cURL like cross site forgery attacks.This is why any cURL script must contain the csrf token of the target page to it's post parameters.

You must first locate the token from your target page and then write code so that your script will parse the token out of the curl_exec output string.

You have to use