{"issue":{"pull_request":{"diff_url":null,"html_url":null,"patch_url":null},"state":"open","user":{"avatar_url":"https://secure.gravatar.com/avatar/025a89573f7c7616fda772eee19390a7?d=https://a248.e.akamai.net/assets.github.com%2Fimages%2Fgravatars%2Fgravatar-140.png","gravatar_id":"025a89573f7c7616fda772eee19390a7","url":"https://api.github.com/users/marklochrie50265","login":"marklochrie50265","id":218651},"milestone":null,"labels":[],"updated_at":"2011-10-28T00:14:47Z","assignee":null,"comments":2,"closed_at":null,"url":"https://api.github.com/repos/fennb/phirehose/issues/11","body":"Since the recent updates to the Streaming API (SSL) We have been struggling to get the latest version of phirehose to work behind our proxy.\r\n\r\nAfter making minor changes to the phirehose script in order to work with our proxy \r\nThe error log we are getting is \r\n\r\nError: [Tue Oct 18 13:59:37 2011] [error] [client 194.80.32.10] Phirehose: Connecting to twitter stream: https://stream.twitter.com/1/statuses/filter.json with params: array (  'delimited' => 'length',  'track' => '#x$\r\n[Tue Oct 18 13:59:37 2011] [error] [client 194.80.32.10] Phirehose: Resolved host stream.twitter.com to 199.59.148.138\r\n[Tue Oct 18 13:59:37 2011] [error] [client 194.80.32.10] Phirehose: Connecting to 199.59.148.138\r\n[Tue Oct 18 13:59:37 2011] [error] [client 194.80.32.10] Phirehose: Full URL: ssl://199.59.148.138:443\r\n[Tue Oct 18 13:59:37 2011] [error] [client 194.80.32.10] Phirehose: TCP failure 20 of 20 connecting to stream: No route to host (113). Sleeping for 16 seconds.\r\n\r\nChanges : $opts = array('http' => array('proxy' => 'tcp://wwwcache.lancs.ac.uk:8080', 'request_fulluri' => true));\r\n         $context = stream_context_create($opts);\r\n\r\n     //@$this->conn = fsockopen($scheme . $streamIP, $port, $errNo, $errStr, $this->connectTimeout,$context);\r\n         @$this->conn = stream_socket_client($scheme . $streamIP . \":\" .$port, $errNo, $errStr, $this->connectTimeout, STREAM_CLIENT_CONNECT, $context);\r\n\r\nWe are now thinking it could be to do with\r\n\r\nOpening an insecure connection to the proxy which then attempts to forward the plain text request to twitter. We were thinking perhaps it can be re-coded using cURL instead of fsock? But we arent sure on this matter.\r\n\r\nThanks\r\n\r\n\r\n\r\n\r\n","html_url":"https://github.com/fennb/phirehose/issues/11","title":"PROBLEM! HTTPS Phirehose via Proxy","number":11,"id":1948357,"created_at":"2011-10-18T15:07:30Z"},"action":"created","comment":{"user":{"avatar_url":"https://secure.gravatar.com/avatar/78aabcb2d118c6ed39b8f18a0a3e58d2?d=https://a248.e.akamai.net/assets.github.com%2Fimages%2Fgravatars%2Fgravatar-140.png","gravatar_id":"78aabcb2d118c6ed39b8f18a0a3e58d2","url":"https://api.github.com/users/DarrenCook","login":"DarrenCook","id":880436},"updated_at":"2011-10-28T00:14:47Z","url":"https://api.github.com/repos/fennb/phirehose/issues/comments/2551201","body":"CURL never seems to be installed by default on any of the server hosting or distros I use, so the lack of dependency on curl is a feature of Phirehose. Though, of course, a minor one.","id":2551201,"created_at":"2011-10-28T00:14:47Z"}}