Unwanted port redirection

[PopiBrossard]

Is this a BUG REPORT or FEATURE REQUEST? (choose one):
BUG REPORT (behavior change since 0.9.0)

NGINX Ingress controller version:
quay.io/kubernetes-ingress-controller/nginx-ingress-controller:0.9.0

Kubernetes version (use kubectl version):
1.7.11

Environment:

• Cloud provider or hardware configuration: Bare metal, amd64
• OS (e.g. from /etc/os-release): Ubuntu 16.04.3 LTS (Xenial Xerus)
• Kernel (e.g. uname -a): 4.4.0-96-generic
• Install tools: kubeadm
• Others:

What happened:
When redirecting an URL the ingress controller specify the port given by the option --https-port (if the port is not the default 443 port for https). This change is due to #1769 .

The problem is that my ingress controller is behind a load balancer, and the port used between these 2 equipments (40443) aren't the same as the public port (443) on the load balancer:
[end user] -->443[Load Balancer]40443-->40443[Ingress Controller]-->[Some services].

So after the redirection the user won't be able to access the website because he will try to contact the Load Balancer on the closed port 40443.
If I use the version quay.io/kubernetes-ingress-controller/nginx-ingress-controller:0.9.0-beta.19 the problem is gone.

What you expected to happen:
The ingress controller should do the same things as before (don't set the https ports in http to https redirections) or I should be able to specify the public https port for redirects.

How to reproduce it (as minimally and precisely as possible):
Setup an ingress controller with --https-port=40443, add a http to https redirect rule to an ingress rule. The redirect will specify the 40443 port (redirect to https://some-domain:40443/).

[aledbf]

@PopiBrossard I will add a flag to make this redirection configurable when custom ports are used