Twitter REST API v1.1 appears to require non-empty Content-Length on POST

[pavemen]

A bit of an FYI:

I used to use tmhAOuth 0.14 and the Twitter API v1 without any issue and I could delete a status via

$tmhOAuth->request('POST', $tmhOAuth->url('1/statuses/destroy/'.$id));

when I upgraded to tmhOauth 0.70 and the new Twitter REST API v1.1 was released, this no longer works and was getting a '411 Content-Length Required' message. I have to provide a non-empty array to the post param attribute

$tmhOAuth->request('POST', $tmhOAuth->url('1.1/statuses/destroy/'.$id), array('dummy'=>'dummy'));

and it all works fine now.

[neave]

Thanks @pavemen has this been filed at https://dev.twitter.com/issues anywhere do you know?

[themattharris]

duplicate of #94, we'll track this under that ticket instead.

[rasa]

Bug filed here: https://dev.twitter.com/issues/643