Path-Based-Routing is broken
- Dominant language
- TypeScript
- Stars
- 22.8k
- Forks
- 783
- Avg merge
- 1d 7h
- Merged PRs (30d)
- 52
Description
### Describe the Bug
Multiple targets on a single domain act as load balancers regardless of match-path rules or priority.
### Environment
- OS Type & Version: (e.g., Ubuntu 22.04)
Ubuntu 22.04
- Pangolin Version:
1.14.1
- Gerbil Version:
Latest
- Traefik Version:
Latest
- Newt Version:
1.8.1
- Olm Version: (if applicable)
N/A
### To Reproduce
Set a path based rule, and try to trigger it. For example set the following rules on any resource:
Prefix: "/" -> 192.168.1.7:3000
Prefix: "/api" -> 192.168.1.7:3001
The backend service that is returned will be random, completely ignoring PBR rules.
I have also tried only setting a single prefix rule for "/api", and changing priorities to be equal, above, below, equal non-100, and non-100 above/below.
Regardless, the service returned is random.
### Expected Behavior
domain.com would route to the service on 192.168.1.7:3000 and domain.com/api (or /api/share etc.) would route to the service on 192.168.1.7:3001.
Contributor guide
Assessment
This issue has not been assessed yet.