Multiple Ingress backends ignored when SSL Passthrough is enabled

[KashifSaadat]

I recently had a setup with an ingress resource configured similar to below (trimmed down):

kind: Ingress
metadata:
  annotations:
    nginx.ingress.kubernetes.io/ssl-passthrough: "true"
...
spec:
  rules:
  - host: example.com
    http:
      paths:
      - backend:
          serviceName: web
          servicePort: 8443
        path: /
      - backend:
          serviceName: api
          servicePort: 8443
        path: /api

Currently what happens is the second backend is not added to the configuration and requests are sent to the root, with the following log line being produced:

W0317 11:57:17.176369       8 controller.go:427] Ignoring SSL Passthrough for location "/api" in server "example.com"

This looks to be intended behaviour according to the code, would anyone be able to shed some light on why that is so I can understand better as I'm probably overlooking some flaw in my approach. If not then I can look at raising a PR to amend it.

NGINX Ingress controller version: v0.28.0
Kubernetes version: v1.15.7

/kind bug

[aledbf]

nginx.ingress.kubernetes.io/ssl-passthrough: "true"

When you use SSL passthrough NGINX cannot read the content of the connection.

[KashifSaadat]

Ah of course, thanks!