In MS IIS, it's possible to bind a web server to a specific host name.
Is the same possible in Jetty?
I have one site running in IIS and another address for Metabase. I'd prefer not to use ports other than 443.
Please don't tell me to read the Jetty manual. Like 99% of open source software, it doesn't help in the slightest. I'm hoping someone else has done this already.
Hi @AndrewMBaines
Jetty is listening on the network interface (meaning the IP address), not the Windows hostname.
By default Jetty listens on localhost interface (if running the JAR), so it should automatically only be available on the server itself, not other network interfaces.
I don't know if you want to use IIS as a reverse-proxy, but it sounds like that, so you can handle certificates/etc through that.
Nothing to do with the windows hostname.
I have two sites I want addressed via https://report.customername.co.uk and https://dashboard.customername.co.uk. In IIS, I can specify which site takes which requests. I can do the same in Apache Tomcat. I'm assuming there must be a way to do in Jetty.
I'll take a look at using IIS as a reverse-proxy but I'm wary of overcomplicating things.
@AndrewMBaines But you can only have a single process listening on a specific port, so if you make Jetty listen on the port, then you cannot have IIS.
You are not over-complicating by using IIS as a reverse-proxy, since it's already running and it can manage certificates.