shrutikohli / yourtwapperkeeper

Automatically exported from code.google.com/p/yourtwapperkeeper
Other
0 stars 0 forks source link

Stream API will switch to SSL - Supported? #5

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago
Hi, I'm having an issue with Stream API SSL. Have tried editing Phirehose.php, 
but it simply will not connect.

Simply changing from:

const URL_BASE = 'http://stream.twitter.com/1/statuses/';

to:
const URL_BASE = 'https://stream.twitter.com/1/statuses/';

fails.

https://github.com/fennb/phirehose/issues/9 
Here they suggest to edit Oauth also, however, how do one do that in 
yourtwapperkeeper?

From the source:

All our Streaming API products are now supporting SSL and we've just updated 
the Streaming API Methods [1], User Streams [2] and Site Streams [3] 
documentation pages accordingly.

As we're planning to sunset HTTP support in about a month, we strongly 
encourage you to switch to SSL (HTTPS) as soon as possible, especially if 
you're still authenticating your Streaming API requests with Basic Auth. On a 
related note, Basic Auth will eventually be deprecated on the Streaming API, 
and we recommend that you switch to OAuth well in advance.

Implementation changes on your side should be as simple as changing http 
protocol for https

Streaming API: use https://stream.twitter.com instead of 
http://stream.twitter.com
User Streams: you should already be using https://userstream.twitter.com
Site Streams: you should already be using https://sitestream.twitter.com
Just like for api.twitter.com, we are using Verisign SSL certificates on these 
domains. If for some reason you need the Verisign Root CA Certificate, you can 
obtain it directly from Verisign, or from this link: 
http://curl.haxx.se/ca/cacert.pem

1) i:/C=US/O=VeriSign, Inc./OU=Class 3 Public Primary Certification
Authority - G2/OU=(c) 1998 VeriSign, Inc. - For authorized use
only/OU=VeriSign Trust Network

On September 29th, the Streaming API will turn SSL only. While one month’s 
time is our plan, please be sure to give us your feedback on this discussion 
thread [4] if you think you needed more time. As always, if you have questions 
about the Streaming API, let us know on our Developers Discussions board.

[1] https://dev.twitter.com/docs/streaming-api/methods
[2] https://dev.twitter.com/docs/streaming-api/user-streams
[3] https://dev.twitter.com/docs/streaming-api/site-streams
[4] https://dev.twitter.com/docs/security/public-key

Blog URL: 
https://dev.twitter.com/blog/streaming-api-turning-ssl-only-september-29th
Please do not reply to this message; it was sent from an unmonitored email 
address. Visit https://dev.twitter.com/user to manage your subscriptions.

Original issue reported on code.google.com by audun.ut...@me.com on 2 Sep 2011 at 10:50

GoogleCodeExporter commented 8 years ago
Also make a change to the following line in Phirehose.php:

FROM:
@$this->conn = fsockopen($scheme . $streamIP, 80, $errNo, $errStr, 
$this->connectTimeout);

TO:
@$this->conn = fsockopen($scheme . $streamIP, 443, $errNo, $errStr, 
$this->connectTimeout);

I hope to uploaded updated files later today.

John

Original comment by jobr...@ob3solutions.com on 4 Oct 2011 at 12:32