Describe the bug SCG as ssl termination doesnt work any longer. When SCG listens on https but the downstream clients are using http and when using loadbalancer such as Eureka the SCG tries to use https for downstream.

Reason for the bug

  1. org.springframework.cloud.netflix.eureka.EurekaServiceInstance doesnt implement org.springframework.cloud.client.ServiceInstance#getScheme so it returns null
  2. As fallback for scheme was null following method uses original uri scheme org.springframework.cloud.client.loadbalancer.LoadBalancerUriTools#computeScheme

As a result instead of using http protocol it is using https protocol

Comment From: spencergibb

You can force ssl with lbs scheme IIRC

Comment From: sabareeshkkanan

@spencergibb Actual problem is reverse. My down stream service doesnt use ssl and when the register to eureka they dont use secure port but Gateway is using https to downstream and fails

Comment From: jayzch

Describe the bug SCG as ssl termination doesnt work any longer. When SCG listens on https but the downstream clients are using http and when using loadbalancer such as Eureka the SCG tries to use https for downstream.

Reason for the bug

  1. org.springframework.cloud.netflix.eureka.EurekaServiceInstance doesnt implement org.springframework.cloud.client.ServiceInstance#getScheme so it returns null
  2. As fallback for scheme was null following method uses original uri scheme org.springframework.cloud.client.loadbalancer.LoadBalancerUriTools#computeScheme

As a result instead of using http protocol it is using https protocol

Yes, I fully agree. I think it should use http as defualt.