Hi, first of all, thanks for maintaining this project.
I encountered a domain matching priority issue when using HTTP/HTTPS host forwarding.
Current setup
Example rules:
*.example.com -> 127.0.0.1:80
gateway.example.com -> another target
Both rules are configured in NPS.
Expected behavior
Exact domain rules should have higher priority than wildcard rules.
For example:
should match the exact rule first, instead of being captured by:
This is the behavior used by many reverse proxies/load balancers such as nginx, Traefik, Caddy, etc.
Actual behavior
The wildcard rule:
captures the request first.
The exact rule:
never takes effect.
Environment
- nps fork: djylb/nps
- HTTPS enabled
- TLS termination enabled
- ECS + npc + reverse proxy architecture
Suggestion
It would be great if NPS could:
- Automatically prioritize exact domain matches over wildcard matches
- Or provide configurable rule priority/order
- Or document the current matching behavior clearly
This becomes important when using wildcard domains as a generic gateway entry, while reserving several exact domains for infrastructure or management services.
Thanks!
Hi, first of all, thanks for maintaining this project.
I encountered a domain matching priority issue when using HTTP/HTTPS host forwarding.
Current setup
Example rules:
Both rules are configured in NPS.
Expected behavior
Exact domain rules should have higher priority than wildcard rules.
For example:
should match the exact rule first, instead of being captured by:
This is the behavior used by many reverse proxies/load balancers such as nginx, Traefik, Caddy, etc.
Actual behavior
The wildcard rule:
captures the request first.
The exact rule:
never takes effect.
Environment
Suggestion
It would be great if NPS could:
This becomes important when using wildcard domains as a generic gateway entry, while reserving several exact domains for infrastructure or management services.
Thanks!