Route to subpath with more sublevel

Traefik Traefik v2
#1

Hi,
I can't seem to find a way to use a multiple subpaths for a route ex: /customers/customer/service1
My environment test has traefik 2.1 and some instance of containous/whoami:v1.3.0.
This is a code that works well with a single subpath for /who
But I need a multiple subpaths like test.mydomain.om/customers/customer/who, I tried to replace PathPrefix and stripprefix.prefixes string with "test.mydomain.om/customers/customer/who" but it doesn't work. What is the correct syntax? (I work without toeml configuration file but only command option in docker-compose)

thanks

  my-app:
    image: containous/whoami:v1.3.0
    container_name: my-app
    labels:
      - "traefik.enable=true"
      - "traefik.http.routers.my-app.rule=(Host(`test.mydomain.com`) && (PathPrefix(`/who`) ))"
      - "traefik.http.routers.my-app.middlewares=my-app-stripprefix"
      - "traefik.http.middlewares.my-app-stripprefix.stripprefix.prefixes=/who"
      - "traefik.http.routers.my-app.entrypoints=websecure"
      - "traefik.http.routers.my-app.tls=true"
      - "traefik.http.routers.my-app.tls.certresolver=letsencrypt"
    networks:
      aaa_network:
        ipv4_address: "172.1.0.5"
#2

Please I need help to understand the new rules about subpath routing. In the last version (1.7) i can do this with one single line of code per service in docker compose with PathPrefixStrip label...

#3

I just test your code and it is correct:

services:
    whoami:
        image: "containous/whoami"
        container_name: "whoami"
        labels:
          - "traefik.enable=true"
          - "traefik.http.routers.whoami.rule=Host(`whoami.domain.net`) && PathPrefix(`/who`)"
          - "traefik.http.routers.whoami.middlewares=my-app-stripprefix"
          - "traefik.http.middlewares.my-app-stripprefix.stripprefix.prefixes=/who"
          - "traefik.http.routers.whoami.entrypoints=websecure"
          - "traefik.http.routers.whoami.tls.certresolver=OVH"
          - "traefik.http.services.whoami.loadbalancer.server.port=80"
        networks:
             frontend:
                ipv4_address: 172.19.0.20

networks:
    frontend:
        external:
            name: traefik_network

https://whoami.domain.net/who/am/i

Hostname: b8815a72c662
IP: 127.0.0.1
IP: 172.19.0.20
RemoteAddr: 172.19.0.9:56654
GET /am/i HTTP/1.1
Host: whoami.domain.net
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:73.0) Gecko/20100101 Firefox/73.0
Accept: text/html,application/xhtml+xml,application/xml;q=0.9,image/webp,*/*;q=0.8
Accept-Encoding: gzip, deflate, br
Accept-Language: fr,fr-FR;q=0.8,en-US;q=0.5,en;q=0.3
Dnt: 1
Te: trailers
Upgrade-Insecure-Requests: 1
X-Forwarded-For: redacted
X-Forwarded-Host: whoami.domain.net
X-Forwarded-Port: 443
X-Forwarded-Prefix: /who
X-Forwarded-Proto: https
X-Forwarded-Server: f8ff1876f322
X-Real-Ip: redacted

remove any unnecessary parenthesis in your condition :

Host(`whoami.domain.net`) && PathPrefix(`/who`)
#4

Thanks @Minikea
did you try to use the API route of whoami container?
If I curl the container directly
curl 172.1.0.2/api
I can get the correct answer in json like:
{"hostname":"c888c0c482d0","ip":["127.0.0.1","172.1.0.2"],"headers":{"Accept":["*/*"],"User-Agent":["curl/7.58.0"]},"url":"/api","host":"172.1.0.2","method":"GET"}

If I try to use a curl to the route test.mydomain.com/who/api I still get the same answer than root / call test.mydomain.com/who, but the "GET" value have correct route

Hostname: c888c0c482d0
IP: 127.0.0.1
IP: 172.1.0.2
RemoteAddr: 172.1.0.4:60318
GET /who/api/ HTTP/1.1

Did you see the same problem?
Did you try with multiple subpath like test.mydomain.com/customer1/who/api ?

Thanks