Gateway httpsRedirect now being 'ignored' - how to verify

Config
1

I’ve got a pretty simple EKS cluster, with an Istio Gateway defined to redirect http requests on port 80 to https. Was working fine for approximately 5 weeks.
Now http requests are resulting in 404 responses.

I’ve looked through the Pilot Pod’s log for any indication regarding the use of the httpsRedirect with no luck.

Hopefully someone can suggest where to look to confirm this redirect should be functioning. Nothing in the /etc/istio/proxy/* files in the istio-ingressgateway* pod is jumping out at me.
Related to this, the istioctl proxy-config routes istio-ingressgateway-7488fd6597-wl9qn.istio-system -o json is now showing that port 80 is a Blackhole service. Rather than doing the redirect as was working.
curl requests directly to 443 are working fine, get routed to the correct pod & responses are as expected.

Any pointers greatly appreciated. Thanks.

2

Probably not your specific case, but in my config, after I used for hosts “namespace/my.hostname.io” in the Gateway, httpsRedirect stopped working.
After changing it to a wildcard, it fixed the problem.

3

Hi,

Justed wanted to respond that I also encountered some issues with httpRedirect: true not working (getting http404 on http:// calls).
The cause was that in my VirtualService configuration, I only had http routes that match port 443.
Adding a dummy route that matched port 80, or removing the port: 443 criteria from the match criteria resolved the issue.

I think its a bit strange that this is necessary, and I’m not sure of this is a bug.
If I redirect traffic from http (port 80) to https (443) on the Gateway, I would not expect that the http traffic still gets matched against the VirtualService routes.