Re: [jetty-users] UPDATE: calling setHost under jetty v9.4.8.v20171121 c

[west suhanic <west.suhanic@xxxxxxxxx>]

Hi Greg:

Thanks for the reply.

I can indeed ping the machine aaa.bbb.ccc from the client machine and get the expected IP address of  192.168.20.9.

I did write a small piece of code which populates an array of InetAddress. The first element in the array

contains 127.0.0.1 and the second contains  192.168.20.9. My /etc/hosts file is configured this way

because of another application. So the work around I have is to  populate InetAddress array and use the non-local

host IP address in the setHost call. This solves my problem and maintains my non-standard configuration.

thanks,

west suhanic

On Tue, Dec 12, 2017 at 2:25 PM, Greg Wilkins <gregw@xxxxxxxxxxx> wrote:

West,

Sounds like there could be some DNS resolution problems on your machine.

Can you do a host lookup for "aaa,bbb.ccc" and get 192.168.20.9? from the command line?

Perhaps try writing a little test main in java to check that InetAddress can also look up the name and resolve it.

regards

On 12 December 2017 at 20:08, west suhanic <west.suhanic@xxxxxxxxx> wrote:

Hello:

This is an update to my previous email.

If I use an actual IP address in the setHost call everything works as expected.

For example:

 ServerConnector http = new ServerConnector(server,
                new HttpConnectionFactory(http_config));
 http.setPort(8080);
 http.setHost( "192.168.20.9" );
 http.setIdleTimeout(30000);

works as expected when contacted using the following URL:

http://aaa.bbb.ccc:8080/index.html

thank you,

west suhanic

_______________________________________________
jetty-users mailing list
jetty-users@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/jetty-users

--

Greg Wilkins <gregw@xxxxxxxxxxx> CTO http://webtide.com