Quantcast
Channel: Tweetinvi a friendly Twitter C# library
Viewing all articles
Browse latest Browse all 4126

Commented Issue: Twitter to require SSL/TDS [1946]

$
0
0
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: cyberlogan1973 **

Hi Linvi,

I downloaded the latest development branch yesterday and was able to compile the source code. However, when deploying the new code I am receiving a 403 Forbidden error.

The remote server returned an error: (403) Forbidden.

According to the Twitter:

403 Forbidden The request is understood, but it has been refused or access is not allowed. An accompanying error message will explain why. This code is used when requests are being denied due to update limits.

I find it difficult to believe I am reaching our request limit, as there is only one code base accessing the API and it's currently not working.

I followed the examples from the Example program in the source code, so I am fairly certain I am using the Tweetinvi API correctly.

Do you have any suggestions as to what the problem may be or any further steps I can take to diagnose the issue?


Thank you,

Dan


Viewing all articles
Browse latest Browse all 4126

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>