Is there a known bug with Version /1.1 and POSTing with spaces in the content?


Hi I’m writing a library that works perfectly for everything on the /1 endpoint (get tweets, post tweets etc). It also works perfectly for everything on the /1.1 endpoint EXCEPT for when POSTs (in this case the update status endpoint) has spaces in the content (e.g. ‘status->hello’ works fine but ‘status:->hello world’ fails). I’m correctly percent encoding the status value before it gets added into the signature and added as post params. Any explanation for this behavior? Thanks!


Space characters aren’t valid in query strings or POST bodies and API v1.1 more strictly enforces this. You should encode space characters as “%20” and in the signature basestring it should be represented as “%2520”


Thank you - I wasn’t double encoding in the base string