On Thu, May 20, 2010 at 4:16 PM, Taylor Singletary
> Hi Damon,
> We've heard some reports of iPads setting their dates/clocks incorrectly --
> sometimes back to 1969. If the client application uses the date/time on the
> machine (rather than querying it from some other source), and the date/time
> isn't within 5 minutes or so of our clocks, it results in a failed request.
> One work around is for clients to adjust their concept of the "current time"
> by looking at the HTTP headers we send on a failed request (which includes
> our server clock), or to use an external service to fetch the time prior to
> making a request.
> Taylor Singletary
> Developer Advocate, Twitter