X-Forwarded-Prefix annotation adding //

[dwilliams782]

Following on from a request for help which got closed:

#3119

I was trying to replicate the behaviour of x-forwarded-prefix, and eventually I found that this annotation was added back in December, but it hasn't been added to the docs that I can see?

"nginx.ingress.kubernetes.io/rewrite-target": "/",
"nginx.ingress.kubernetes.io/x-forwarded-prefix": "true"

I'm trying to route on /namespace/ which is current working, for example /default/ will now route to the default/gateway-svc as expected, but in the url, I end up with two //:

default**//**ui/#/

"rules": [
      {
        "http": {
          "paths": [
            {
              "path": "/default",
              "backend": {
                "serviceName": "gateway",
                "servicePort": 8080
              }
            }
          ]
        }
      }
    ]

I've played around with the annotations, but I think my application is redirecting to /ui/, not sure where the additional '/' is coming from. If I manually remove one of them from the URL, it works as expected. Any ideas?

[dwilliams782]

Having reviewed the nginx.conf generated, nginx is adding a trailing / to the path:

proxy_set_header X-Forwarded-Prefix "/default/";

Looks like this is a bug in my opinion.

[dwilliams782]

"nginx.ingress.kubernetes.io/configuration-snippet": "proxy_set_header X-Forwarded-Prefix /default;",
"nginx.ingress.kubernetes.io/rewrite-target": "/"

This works though! Hope this helps anyone else that gets stuck on this like I did.

I still consider this a bug, because if I had more than one path / service for this namespace, I would have to create individual ingresses. It might be able to be handled by the application performing the redirect to not append /, but the prefix should be the literal matching string. Any thoughts?

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

[fejta-bot]

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten

[fejta-bot]

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close

[k8s-ci-robot]

@fejta-bot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.