Priority not computed correctly

Traefik Traefik v2
,
1

I noticed that the priority feature doesn't work at all. Neither setting the priority manually via labels or trying to force a higher priority by making the rule longer affect the order which causes my HTTPS redirect to fail and my path match to have no effect.

grafik

grafik
grafik1037×54 6.53 KB

2

Hello @SIMULATAN,

The dashboard is sorted alphabetically using the router's name. This view does not show the rule priority.

To know what priority was applied, you can look for them in the DEBUG log.

Home it helps :smiley:

3

That's good to know!

I saw that the priority property got picked up by traefik in the "configuration received" log line:

"http": {
 "routers": {
  "highscores": {
                "entryPoints": [
                    "http"
                ],
                "service": "highscores",
                "rule": "Path(`/highscores`) || Host(`this-is-just-some-thing-to-make-the-priority-high.com`)",
                "priority": 7000
            }
  }
}

I noticed that this specifc route indeed got registered BEFORE any other route. I just tried it again and it actually does seem like it gets registered before other routes. I'm still a little bit confused to how the priority works but that already helps, thanks!

4

Turns out I didn't read the rule docs well enough, I just assumed the Host rule would allow wildcards which it doesn't and now everything works as intended. Thank you very much for your help!

1 Like