Does this lb support traefik's PathPrefixStrip like feature about nghttpx-ingress-lb HOT 6 CLOSED

FYI, next version of this ingress controller will have per-backend mruby scripting, which kicks in after backend has been chosen. It will be the bast place to rewrite request path.

from nghttpx-ingress-lb.

There is no feature to strip path prefix at the moment.
nghttpx supports mruby user script which can alter request path, but it happens before routing a request to the backend. If I understand it correctly, you need to rewrite path after determining backend service.

from nghttpx-ingress-lb.

@tatsuhiro-t thanks for your comment. Yes, that is correct, I need to rewrite path after determining backend service.

Do you mean to say that when mruby script executes, the backend service has not yet been determined based on path matching, so rewriting path there would cause it to fail the match?

I may have to modify the application code itself to honor the prefix if I cannot strip it.

from nghttpx-ingress-lb.

Also, maybe there is the possibility of defining the matching paths to just be filing, public and admin in my example, but let consumers use the prefix.

Then, in the mruby script, rewrite path to not have prefix. Then path matching should pass.

from nghttpx-ingress-lb.

Do you mean to say that when mruby script executes, the backend service has not yet been determined based on path matching, so rewriting path there would cause it to fail the match?

Yes

Also, maybe there is the possibility of defining the matching paths to just be filing, public and admin in my example, but let consumers use the prefix.

Then, in the mruby script, rewrite path to not have prefix. Then path matching should pass.

I think it works. You might need to do some actions to prevent consumer from accessing /public directly in mruby if it is required.

from nghttpx-ingress-lb.

@tatsuhiro-t thanks for trying to help out. It seems any kind of mruby manipulation of the path ends up dictating later decision making of choosing the backend fail in my case. My line of thought would only work if mruby kicked in after backend was chosen.

In any case, I got this to work for my use-case:

apiVersion: extensions/v1beta1
kind: Ingress
metadata:
  name: hmda-platform-ingress
spec:
  rules:
  - host: 'filing.myhmdaapp.com'
    http:
      paths:
      - path: /
        backend:
          serviceName: hmda-platform-api
          servicePort: filing
  - host: 'admin.myhmdaapp.com'
    http:
      paths:
      - path: /
        backend:
          serviceName: hmda-platform-api
          servicePort: admin
  - host: 'public.myhmdaapp.com'
    http:
      paths:
      - path: /
        backend:
          serviceName: hmda-platform-api
          servicePort: public

Then accessing whichever one using the correct Host headers.

curl -H "Host: filing.myhmdaapp.com" -i http://ingress-address

Closing this issue for now.

from nghttpx-ingress-lb.