Upayavira wrote:
I have logged into another PC with PCAnywhere and tried http://charya:8889. (My PC is charya). It didn't work. I removed the Host line, and restarted, and it did.
I guess that is reasonably conclusive, isn't it? ;-)
Mmmh. Not neccessarily. If the default is to bind to your NIC's public IP (i.e. with no host line), then you'd be able to access Jetty from any computer that can reach that public IP address.
As a test I set the host to my public IP address, and I get the following message when I start Jetty:
17:55:04.016 EVENT Started SocketListener on 0.0.0.0:8888 17:55:04.016 EVENT Started [EMAIL PROTECTED] 17:55:04.086 EVENT Starting Jetty/4.2.9 17:55:04.096 EVENT Started ServletHttpContext[/] 17:55:04.106 EVENT Started SocketListener on [MY_PUBLIC_IP_ADDRESS]:8889 17:55:04.106 EVENT Started [EMAIL PROTECTED]
And I was able to access the admin servlet from over the Internet. Likewise, when i set it to 127.0.0.1:
17:56:17.511 EVENT Started SocketListener on 127.0.0.1:8889
And I can only reach the machine from "localhost" (aka 127.0.0.1)
It's the IP address it binds to, I tell you! :)
Ah. Gocha. It is the interface on which it listens. And if it listens on loopback (127.0.0.1), it'll only hear requests from localhost. If you skip the Host parameter, it'll listen on all interfaces.
Makes sense.
Regards, Upayavira
