Whether to support the rest client that supports unix sockets

[wzzc-dev]

security-api/mp-rest/url: unix:///opt/tmp/eulixspace-security-agent.sock

I have added the --enable-url-protocols=unix parameter to the configuration file

but error：

Caused by: java.net.MalformedURLException: Accessing an URL protocol that was not enabled. The URL protocol unix is not tested and might not work as expected. It can be enabled by adding the --enable-url-protocols=unix option to the native-image command

[quarkus-bot[bot]]

/cc @Sgitario, @cescoffier, @geoand

[geoand]

@cescoffier does the Vert.x HTTP Client support the UNIX socket protocol?

[cescoffier]

Yes, but only in JVM mode and you need to enable native transport (and pick the one you want - epoll I presume).

See: https://quarkus.io/guides/vertx-reference#native-transport

[geoand]

🙏

[dorianm]

We use Quarkus in native mode, do you have a recommendation to call an HTTP service through a Unix Socket in this case? I was considering using Vert.x HTTP Client until I saw this discussion.

[wzzc-dev]

Native transports are not supported in GraalVM produced binaries.

[cescoffier]

Yes, at the moment, we do not support domain sockets in native. It requires making Netty native transport work in native executables, and we never prioritized that work. Native transport brings a concurrency benefit that gets a bit reduced by the native compilation.

[dmlloyd]

Since Java 17 is our baseline, could/should we look into Netty using NIO support for UNIX domain sockets (which is available since Java 16)?

[cescoffier]

@dmlloyd Yes, it's something I added to my to-do list almost a year ago...