Not quite sure what's going on but here's a successful run I just did:

POST body:
status=LOAD%20"*",8,1

Signature base string:
POST&http%3A%2F%2Fapi.twitter.com
%2F1%2Fstatuses%2Fupdate.xml&oauth_consumer_key%3Dri8JxYK2ddwSV5xIUfNNvQ%26oauth_nonce%3DPKDmiV56WcizhiJA0RYw2dxyvlisSSJGdbZPMMYujM%26oauth_signature_method%3DHMAC-SHA1%26oauth_timestamp%3D1276453540%26oauth_token%3D119476949-gF0B5O1Wwa2UqqIwopAhQtQVTzmfSIOSiHQS7Vf8%26oauth_version%3D1.0%26status%3DLOAD%2520%2522%252A%2522%252C8%252C1

Different kinds of so-called URL encoding in the world make this process
harder.

http://www.marcworrell.com/article-2943-en.html

Taylor Singletary
Developer Advocate, Twitter
http://twitter.com/episod


On Sun, Jun 13, 2010 at 9:35 AM, rhysmeister <[email protected]>wrote:

> I can't currently use asterisk characters in my app. If this is
> included in a status update then I get an incorrect signature error
> returned. In my signature base I'm encoding * as %252A and the status
> update contains %2A. I'm doing similar syuff for other characters with
> success but this just doesn't work. I've been using this site to help
> http://developer.netflix.com/resources/OAuthTest and as far as I can
> tell all my output is spot on. Anyone know what might be going on
> here?
>
> Cheers,
>
> Rhys
>

Reply via email to