sudeeptoroy

yes, these changes were done too..

https://github.com/envoyproxy/envoy/blob/feb56a1f8ee2cf1ea2048e20b7ba05f8199355c6/api/envoy/api/v2/route/route.proto#L954 this seems to be missing while programming the envoy configuration for redirect

>When Envoy is configured to redirect a request from HTTP to HTTPS it is appending a port number. For standard ports 80 and 443, no. This is correct behaviour. However...

@davecheney envoy would not add ports until you program it that way. essentially https://github.com/envoyproxy/envoy/blob/feb56a1f8ee2cf1ea2048e20b7ba05f8199355c6/api/envoy/api/v2/route/route.proto#L954 need to be programmed only for cases when envoy is serving non standard ports; ie http://foo.com:8000...

> We discussed this in a community meeting today. > > Up until now, we have been directing people towards external authentication as a way to implement OIDC. However, as...