What are people generally using as best practice for SSL termination when they need to use socket.io these days?
I'm usually a big fan of nginx, but hear it just doesn't work with socket.io, and don't want to spend hours getting it there. We have multiple backends that get serviced, and would like some kind of load balancing where possible. We have enough IPs (I think) that we can host each backend on an individual IP, so we don't need to do name based SSL. Options I'm considering: stud -> node haproxy -> stud -> node apache -> node (I know everyone hates Apache these days, but it is rock solid, I'm just not sure if it supports what socket.io needs?) stunnel -> node Alternatives? What is best practice? I don't want to let node do SSL. It's too slow at it (and yes I know this is being worked on), so node-http-proxy is out. Matt. -- Job Board: http://jobs.nodejs.org/ Posting guidelines: https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines You received this message because you are subscribed to the Google Groups "nodejs" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/nodejs?hl=en?hl=en
