jersey-container-jdk-http ignores host and always binds to wildcard address

[jerseyrobot]

When using the jersey-container-jdk-http to create a HttpServer, the configuration is passed via an URI, from which protocol, port and path is extracted and used.
Yet, it is not possible to bind the server to the localhost/loopback interface. The HttpServer is always bound to the wildcard address via HttpServer.create(new InetSocketAddress(port), 0)

I would prefer to be able to manually bind the HttpServer at a later time, there should be no need to bind the HttpServer at construction. For the constructor, isHttps and path should be sufficient.

If this change is too complicated, it would help to actually use the host part of the URI for the InetSocketAddress

Affected Versions

[2.22.2]

[jerseyrobot]

@glassfishrobot Commented
Reported by rwma

[jerseyrobot]

@glassfishrobot Commented
dmitri.priimak said:
Similar issue affects SimpleContainerFactory.create(...) method. And it can be solved easily by changes in method

SimpleContainerFactory#_create(URI, SSLContext, SimpleContainer, UnsafeValue<Server, IOException>)

in line 277 where InetSocketAddress is created ignoring hostname part of the URL.

[jerseyrobot]

@glassfishrobot Commented
This issue was imported from java.net JIRA JERSEY-3111

[jerseyrobot]

• Issue Imported From: https://github.com/jersey/jersey/issues/3383
• Original Issue Raised By:@glassfishrobot
• Original Issue Assigned To: @mpotociar