-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
Update Eureka client status URL based on SSL configuration #1843
Comments
Can you show us the configuration that you think should work? |
This should configure the statusPageUrl as All eureka meta url's are configured to I can specify an explicit url, but will the above not be easier? Moreover, if I specify a different management port it configures it properly. |
Is that all of the configuration? Shouldnt you also be enabling SSL via Spring Boot configuration? |
Yes. I think I have that. Here is my full configuration
Am I missing some other ssl configuration? |
Looks like your configuration is a little off, it should be
As far as the status page URL goes, looks like this was discussed in #176. Looks like the behavior you are observing has been that way for a while. Does it effect other service discovery clients? |
Hmm... but everything works fine with my current configuration and <hostName>172.25.1.2</hostName>
<app>TEST-APP</app>
<ipAddr>192.168.1.2</ipAddr>
<status>UP</status>
<overriddenstatus>UNKNOWN</overriddenstatus>
<port enabled="false">8081</port>
<securePort enabled="true">8081</securePort>
Except for the status page url and other health check url's everything works fine. Are there any plans to change that (auto configure the url's) or should I just provide the absolute url in my config file? |
I am going off what our documentation states about registering secure applications. I would stick with what the documentation states. We dont have any plans that I know of to change how things work. We can mark this issue an an enhancement and if we get enough interest in making the change we can take a look at it. Or if you (or someone else) would like to submit a PR for the change that is always welcome as well. |
Ok. Thanks for your help and clarificaitons. |
I think it's will be interesting to make it auto configurable. |
I don't understand why |
with this configuration
the
|
@REME-AlarmTILT
|
Hi,
If I use
secure-port
in my configuration and I don't specify themanagement.port
, then spring cloud does not change my eurekastatusPageUrl
and other url's tohttps
.The
if
condition at line number 114 inEurekaClientAutConfiguraiton.java
(spring-cloud-netflix-eureka-client: 1.2.6 release) prevents it from changing the scheme and it lets netflix configure the url . In netflix'sInstanceInfo.java
there is no check for secure port and the protocol is hardcoded tohttp
.I am not sure where to raise this issue, but since I am using spring-cloud-netflix I am putting this here
The text was updated successfully, but these errors were encountered: