Modify changes feed to use connection protocol so it will work with secure connections

Currently using a secure connection and monitoring for changes will cause the changes socket to die, crashing the node process 

```Error: socket hang up
    at createHangUpError (http.js:1124:15)
    at Socket.socketCloseListener (http.js:1173:23)
    at Socket.emit (events.js:88:20)
    at Array.0 (net.js:335:10)
    at EventEmitter._tickCallback (node.js:190:38)```

This is because the changes feed uses a hard-coded http protocol.  This pull request fixes this in combination with https://github.com/cloudhead/cradle/pull/176

My git-fu is not strong enough to figure out how to clean up the commit but the change is trivial.