Update TokenCreator to only use https queries.
In case anyone has not seen this, here is the link: [https://dev.twitter.com/discussions/24239](http://www.example.com)
> This is an important notice for developers still using HTTP plaintext connections. On January 14th, 2014, connections to api.twitter.com will be restricted to TLS/SSL connections only. If your application still uses HTTP plaintext connections you will need to update it to use HTTPS connections, otherwise your app will stop functioning. You don't need to wait until deadline to implement this change, given that api.twitter.com already supports the recommended environment.
This SSL requirement will be enforced on all api.twitter.com URLs, including all steps of OAuth and all REST API resources.
Comments: ** Comment from web user: linvi **
In case anyone has not seen this, here is the link: [https://dev.twitter.com/discussions/24239](http://www.example.com)
> This is an important notice for developers still using HTTP plaintext connections. On January 14th, 2014, connections to api.twitter.com will be restricted to TLS/SSL connections only. If your application still uses HTTP plaintext connections you will need to update it to use HTTPS connections, otherwise your app will stop functioning. You don't need to wait until deadline to implement this change, given that api.twitter.com already supports the recommended environment.
This SSL requirement will be enforced on all api.twitter.com URLs, including all steps of OAuth and all REST API resources.
Comments: ** Comment from web user: linvi **
Hi,
From Twitter Website :
429 Too Many Requests Returned in API v1.1 when a request cannot be served due to the application's rate limit having been exhausted for the resource. See Rate Limiting in API v1.1.
It means you have posted too many requests on Twitter. This is not at all related with SSL.
Regards,
Linvi