Matt Holt

Hm, I think you _actually_ want #6 -- which is probably a better way to frame the problem. (Closing, but feel free to continue discussion if needed.)

(FWIW I don't mind having breaking changes in this module at this point, it's still early days.)

Use a TLS matcher that matches on SNI, for a route that proxies to the backend you want. I'm mobile right now but hopefully that gives you a quick starting...

@ktmart Ok, so yeah, the last example in our README: https://github.com/mholt/caddy-l4#config-examples Shows how to match routes based on HTTP Host and TLS ServerName. In your case you'd just have multiple...

Ah yeah, that'd be cool. I'd never heard of sshpiper; thanks for the link. I wonder if it can be used as a library. I don't think I have much...

Very nice! Thanks for the tip @tg123. That's very helpful.

The Caddyfile format is itself extensible, and is designed to be interpreted by modules other than the `http` server type. So this is very doable, just needs to be done....

Thanks for the feedback, and the interest in this. I suppose anyone is welcome to contribute this, it would probably be faster than waiting for me to do it on...

It's a big bite to chew if you're new to Go, but I won't stop you. Good luck!

@francislavoie > Right now, too many features are tied to the HTTP Caddyfile so it's not quite viable. I think it depends what you need to do. Currently, the `caddyfile`...