Skip to content

Priortities in 1.0.0 not behaving #506

@bluecmd

Description

@bluecmd

Hi,

I have this frontend config:

  # Special endpoint for traefik mgmt (authed)
  [frontends.mgmt]
  backend = "mgmt"
  priority = 100
  entrypoints = ["authed"]
    [frontends.mgmt.routes.main]
    rule = "Host: traefik.cloud.mydomain.tld"

  # Entry for our cloud services (authed)
  [frontends.cloud]
  backend = "nginx"
  priority = 10
  entrypoints = ["authed"]
    [frontends.cloud.routes.main]
    rule = "HostRegexp: {subdomain:.+}.cloud.mydomain.tld"

To me this means that traefik.cloud.mydomain.tld should go to "mgmt" backend and that rest of the *.cloud.mydomain.tld domains should go to "nginx". This however is not the case. Whatever I try I always get passed to "nginx". Removing the "frontends.cloud" block makes "frontends.mgmt" work the way I want, so I'm guessing it's something related to priorities.

I tried switching the order (that's not very well documented btw, does "100" come before "10"?) and even have only "frontends.mgmt" have the priority, but to no avail.

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions