rust-http supports SSL on the client side but does not on the server side. I am inclined to think this a good idea for the moment, as it is a high-risk area; for that matter, I do not recommend that people have rust-http servers directly facing the Internet for the moment, as there may be DoS attack vectors in it. I recommend sitting it behind a reverse proxy for the moment, such as nginx. For SSL support, I would recommend using something like nginx or stunnel. (This is a security improvement also in case of things like Heartbleed, as the server with most of the sensitive data is in an isolated process.)

Eventually rust-http (or rather, Teepee) will be capable of doing all these things itself, but for the moment—be cautious. For that matter, I don’t recommend that people write web things in Rust yet.

I really think that should be left to nginx or stud or something like that. It's the Unix way, with which I mean, it's less likely someone's going to fuck something up.

Floors author here. I'm glad Chris Morgan answered already because there isn't much I could have told you about that. I'm relying on all the great groundwork Chris already put into rust-http. Keep an eye on http://teepee.rs/. It will soon become the more advanced replacement of rust-http.

teepee looks awesome! Thanks.