Skip to content
This repository has been archived by the owner on Dec 4, 2018. It is now read-only.

Restricting api.twitter.com to SSL/TLS traffic #188

Open
thezerobit opened this issue Dec 27, 2013 · 2 comments
Open

Restricting api.twitter.com to SSL/TLS traffic #188

thezerobit opened this issue Dec 27, 2013 · 2 comments

Comments

@thezerobit
Copy link

According to this
https://dev.twitter.com/discussions/24239
all non-HTTPS API calls will start failing on January 14th.

EpiTwitter.php has this line:

protected $apiUrl         = 'http://api.twitter.com';

I don't know why this particular URL is not using SSL like the rest, but it should probably be changed and tested.

@thezerobit
Copy link
Author

Curl is probably going to want a to certify the endpoint with a CA certificate. I don't know much about PHP/Curl's CA store--if it even has one.

@envelopewindow
Copy link

I used recent ca file from http://curl.haxx.se/docs/caextract.html

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants