When producing an oauth_timestamp for any method requiring authentication,
the time needs to be indicated in seconds since the UTC epoch -- some
programming languages have Date Time classes that deal with epoch time
easily for you, others require more work. In any case, when generating an
oauth_timestamp, you need to take your local time, convert it to UTC, and
then calculate epoch seconds in that timezone. Further, the timestamp needs
to be within ~ 5 minutes of Twitter's server clock. Our server clock is
reported in the Date HTTP header response to each of your requests.
Taylor
On Mon, Nov 1, 2010 at 12:54 PM, Gary cga...@gmail.com wrote:
The system date-time is in sync with local date-time. Exactly what
the English OS is. I'm not sure what timezone it is set to, though.
What else should I take under consideration? Could it be that the
timezone is set to Japan yet the date-time is set to local? (It's not
easy to find my way around this system being that I don't speak/write
Japanese.)
By the way, I have no trouble running two similar apps (on this
machine) that talk with YouTube and Facebook apis.
On Oct 30, 6:10 pm, nischalshetty nischalshett...@gmail.com wrote:
@Gary oAuth takes the current time into consideration, so that really
needs to be in sync.
-N
On Oct 31, 2:56 am, Gary cga...@gmail.com wrote:
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
--
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
