I checked and all characters are utf-8 - the auth header and the post
body.  I tried installing an English OS on the same machine so it's
not machine specific. I also added charset=utf-8 to the content type
header: application/x-www-form-urlencoded; charset=utf-8.  Still I get
the "Failed to validate oauth signature and token".

I'm not sure what the system clock would have to do with it.


On Oct 29, 1:24 pm, Taylor Singletary <taylorsinglet...@twitter.com>
wrote:
> Are there any other environmental issues, such as the system clock that
> might be different? Are you absolutely sure that all characters are UTF-8 in
> both environments, regardless of language?
>
> Taylor
>
> On Fri, Oct 29, 2010 at 1:04 PM, Gary <cga...@gmail.com> wrote:
> > I should add that there are no Japanese characters in the message.
> > It's all English.  In fact I did try adding Japanese characters using
> > the Engllish OS and that worked fine.  Even when I used a Japanese
> > character password, the English OS authenticated correctly.
>
> > On Oct 29, 1:01 pm, Gary <cga...@gmail.com> wrote:
> > > Hi,
>
> > > I've had great success with the Twitter API until I tried it on a
> > > Japanese version of Windows.  It fails to "...validate oauth signature
> > > and token".  I have captured the output using wireshark and the
> > > outgoing message is identical to the English version of Windows.  This
> > > does not happen on all Japanese OS machines, though.
>
> > > Is there a known problem in this area?
>
> > --
> > Twitter developer documentation and resources:http://dev.twitter.com/doc
> > API updates via Twitter:http://twitter.com/twitterapi
> > Issues/Enhancements Tracker:
> >http://code.google.com/p/twitter-api/issues/list
> > Change your membership to this group:
> >http://groups.google.com/group/twitter-development-talk

-- 
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
http://groups.google.com/group/twitter-development-talk

Reply via email to