Path Matching Settings
This reference covers all of Pomerium's Path Matching Settings:
Path
If Path is set, the route will only match incoming requests with a path that is an exact match for the specified path.
How to configure
- Core
- Enterprise
- Kubernetes
Prefix
If Prefix is set, the route will only match incoming requests with a path that begins with the specified prefix.
How to configure
- Core
- Enterprise
- Kubernetes
| YAML/JSON setting | Type | Usage | 
|---|---|---|
| prefix | string | optional | 
Examples
from: https://from.example.com
to: https://to.example.com
prefix: /admin
Set the Prefix in Path Matching settings:

| Name | Type | Usage | 
|---|---|---|
| Prefix | string | optional | 
spec:
  ingressClassName: pomerium
  rules:
    - host: example.localhost.pomerium.io
      http:
        paths:
          - backend:
              service:
                name: example
                port:
                  name: http
            path: /
            pathType: Prefix
See Kubernetes Ingress for more information
Regex
If Regex is set, the route will only match incoming requests with a path that matches the specified regular expression. The supported syntax is the same as the Go regexp package which is based on re2.
How to configure
- Core
- Enterprise
- Kubernetes
Set Regex in the Console:

| Name | Type | Usage | 
|---|---|---|
| path_regex | string | optional | 
Examples
    ingress.pomerium.io/path_regex: 'true'
  name: example
spec:
  ingressClassName: pomerium
  rules:
    - host: example.localhost.pomerium.io
      http:
        paths:
          - backend:
              service:
                name: example
                port:
                  name: http
            path: ^/(admin|superuser)/.*$
            pathType: ImplementationSpecific
