On Apr 12, 8:08 am, Cmdr J0hn <kazuhiro.is...@gmail.com> wrote: > Now, I send a Unicode charactor, "あ " > (not sure displayed on your screen properly, it's Japanese) > > Signed on a string: > > POST&http%3A%2F%2F...(omit)...%26status%3D%25E3%2581%2582 > > And a body is: > > status=%E3%81%82
> Any suggestion anyone? I have exactly the same problem. I have checked with the OAuth signing guide at http://www.hueniverse.com/hueniverse/2008/10/beginners-gui-1.html, which even considers the case of non-English parameters that lead to multibyte characters, and their signature matches mine. I think this is a bug in the way Twitter verifies signatures when multibyte characters are present, and I've filed a bug report with them. Guan
