-
Notifications
You must be signed in to change notification settings - Fork 2.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support non-proxy hosts in REST Client Reactive #22649
Support non-proxy hosts in REST Client Reactive #22649
Conversation
if (nonProxyHosts != null) { | ||
for (String host : nonProxyHosts.split(PIPE)) { | ||
if (!host.isBlank()) { | ||
options.addNonProxyHost(host); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Does it support the format for the JVM nonProxyHosts (e.g. wildcards)?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
yes
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Cool, thanks for confirming.
BTW, I insisted on it because it's very common in enterprise setups to have a proxy for external websites and to have to avoid it for internal sites. And that could happen when using the REST client.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
here's an example from vertx pr that introduced it: eclipse-vertx/vert.x@1e95256#diff-4d9e05c07eed6e23cc3e1e3e32861b7689d8334e963d6bedb7531c00c3853c6aR1031
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Cool, thanks for confirming.
BTW, I insisted on it because it's very common in enterprise setups to have a proxy for external websites and to have to avoid it for internal sites. And that could happen when using the REST client.
sure. I missed it in the original PR, it wasn't omitted intentionally
This workflow status is outdated as a new workflow run has been triggered. Failing Jobs - Building d66bfd0
Failures⚙️ Initial JDK 11 Build #- Failing: extensions/resteasy-reactive/rest-client-reactive/runtime
! Skipped: devtools/bom-descriptor-json docs extensions/oidc-client-reactive-filter/deployment and 16 more 📦 extensions/resteasy-reactive/rest-client-reactive/runtime✖ |
d66bfd0
to
a0d6291
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
This workflow status is outdated as a new workflow run has been triggered. Failing Jobs - Building a0d6291
Full information is available in the Build summary check run. Failures⚙️ JVM Tests - JDK 11 #- Failing: extensions/resteasy-reactive/rest-client-reactive/runtime
! Skipped: extensions/oidc-client-reactive-filter/deployment extensions/oidc-client-reactive-filter/runtime extensions/resteasy-reactive/rest-client-reactive-jackson/deployment and 12 more 📦 extensions/resteasy-reactive/rest-client-reactive/runtime✖
⚙️ JVM Tests - JDK 11 Windows #- Failing: extensions/resteasy-reactive/rest-client-reactive/runtime
! Skipped: extensions/oidc-client-reactive-filter/deployment extensions/oidc-client-reactive-filter/runtime extensions/resteasy-reactive/rest-client-reactive-jackson/deployment and 12 more 📦 extensions/resteasy-reactive/rest-client-reactive/runtime✖
⚙️ JVM Tests - JDK 17 #- Failing: extensions/resteasy-reactive/rest-client-reactive/runtime
! Skipped: extensions/oidc-client-reactive-filter/deployment extensions/oidc-client-reactive-filter/runtime extensions/resteasy-reactive/rest-client-reactive-jackson/deployment and 12 more 📦 extensions/resteasy-reactive/rest-client-reactive/runtime✖
|
a0d6291
to
6de74ac
Compare
No description provided.